Triple
T3613004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Center of the Aerospace Testing Universe |
E76531
|
entity |
| Predicate | describesLocationRole |
P3024
|
FINISHED |
| Object | hub for flight test operations |
—
|
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: hub for flight test operations | Statement: [Center of the Aerospace Testing Universe, describesLocationRole, hub for flight test operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesLocationRole Context triple: [Center of the Aerospace Testing Universe, describesLocationRole, hub for flight test operations]
-
A.
locationDescription
chosen
Indicates a textual description that specifies or characterizes the location of an entity.
-
B.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
C.
placeDescribed
Indicates that one entity provides a description or account of a particular place or location.
-
D.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
E.
introductionLocation
Indicates the place or setting where an introduction or initial presentation of something or someone occurs.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2786f808190be4e42734a79d74e |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.