Triple
T3824373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Pavilion |
E88649
|
entity |
| Predicate | postExpoUse |
P5014
|
FINISHED |
| Object | environmental museum |
—
|
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: environmental museum | Statement: [United States Pavilion, postExpoUse, environmental museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postExpoUse Context triple: [United States Pavilion, postExpoUse, environmental museum]
-
A.
hasExpo
Indicates that an entity hosts, participates in, or is associated with an exposition or exhibition event.
-
B.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
C.
exhibition
Indicates that an entity is organizing, hosting, or serving as a public display or presentation of another entity (such as artworks, objects, or information).
-
D.
subsequentUse
chosen
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
E.
exposed
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.