Triple
T9794478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Where Is Everybody? |
E237684
|
entity |
| Predicate | hasReferenceTo |
P8581
|
FINISHED |
| Object | U.S. Air Force astronaut training |
—
|
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: U.S. Air Force astronaut training | Statement: [Where Is Everybody?, hasReferenceTo, U.S. Air Force astronaut training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferenceTo Context triple: [Where Is Everybody?, hasReferenceTo, U.S. Air Force astronaut training]
-
A.
isReferencedIn
chosen
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
B.
hasCommonReference
Indicates that two or more entities share the same source, citation, or referential basis.
-
C.
hasReferenceURL
Indicates that an entity is associated with a specific web address that serves as a reference or source of additional information about it.
-
D.
hasReferenceID
Indicates that an entity is associated with a specific reference identifier used to uniquely track or distinguish it.
-
E.
hasReferenceWork
Indicates that one entity is associated with a reference work (such as a dictionary, encyclopedia, or manual) that provides authoritative information about it.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda347b6bc8190a99b7dec1650cd46 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.