Triple
T33959177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas history museums |
E870661
|
entity |
| Predicate | typicalExhibitType |
P3934
|
FINISHED |
| Object | permanent exhibits |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: permanent exhibits | Statement: [Texas history museums, typicalExhibitType, permanent exhibits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalExhibitType Context triple: [Texas history museums, typicalExhibitType, permanent exhibits]
-
A.
exhibitionType
chosen
Indicates the specific category or kind of exhibition associated with an entity (e.g., art show, trade fair, scientific exhibit).
-
B.
museumDisplayType
Indicates the manner or format in which items are presented or exhibited within a museum setting.
-
C.
collectionOrExhibition
Indicates that one entity is part of, or presented within, a collection or exhibition organized or maintained by another entity.
-
D.
fieldOfExhibition
Indicates the domain or area in which something is publicly presented, displayed, or exhibited.
-
E.
exhibitionStandard
Indicates that something conforms to, or is used as, the accepted standard or benchmark for exhibitions or displays.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.