Triple
T5817648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury Seven |
E129025
|
entity |
| Predicate | headquartersDuringSelection |
P67132
|
FINISHED |
| Object | Langley Air Force Base vicinity |
—
|
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: Langley Air Force Base vicinity | Statement: [Mercury Seven, headquartersDuringSelection, Langley Air Force Base vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headquartersDuringSelection Context triple: [Mercury Seven, headquartersDuringSelection, Langley Air Force Base vicinity]
-
A.
headquartersFunction
Indicates that an entity serves as the main administrative or central operating location (headquarters) for another entity.
-
B.
headquartersStation
Indicates that a particular station serves as the main headquarters location for an organization or entity.
-
C.
headquartersFor
Indicates that a location serves as the main administrative center or base of operations for an organization or entity.
-
D.
headquartersMunicipality
Indicates the municipality in which an organization’s main administrative headquarters is located.
-
E.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
- F. None of above. chosen
Provenance (4 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c0400dbec08190b2ef73689b2c0c31 |
completed | March 22, 2026, 7:16 p.m. |
Created at: March 22, 2026, 3:53 p.m.