Triple
T7522386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-6 Intruder |
E177802
|
entity |
| Predicate | museumPresence |
P32052
|
FINISHED |
| Object | displayed in multiple aviation museums in the United States |
—
|
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: displayed in multiple aviation museums in the United States | Statement: [A-6 Intruder, museumPresence, displayed in multiple aviation museums in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: museumPresence Context triple: [A-6 Intruder, museumPresence, displayed in multiple aviation museums in the United States]
-
A.
museumHolds
chosen
Indicates that a museum possesses, preserves, or has custody of a particular item or collection within its holdings.
-
B.
museumAt
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
-
C.
hasMuseumAt
Indicates that a museum is located at or exists in a specified place or location.
-
D.
hasMuseumFunction
Indicates that an entity serves the role or performs the function of a museum.
-
E.
museumOpened
Indicates that a museum has begun operating and is officially open to the public from a specific time or date.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c3c4c08190ad418978afcc98ec |
completed | March 27, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.