Triple
T27343344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise (OV-101) |
E684167
|
entity |
| Predicate | initialHomeBase |
P131949
|
FINISHED |
| Object | NASA Dryden Flight Research Center |
—
|
NE NERFINISHED |
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: NASA Dryden Flight Research Center | Statement: [Enterprise (OV-101), initialHomeBase, NASA Dryden Flight Research Center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialHomeBase Context triple: [Enterprise (OV-101), initialHomeBase, NASA Dryden Flight Research Center]
-
A.
homeBaseOf
Indicates that a particular place serves as the primary location, headquarters, or main operational base for an entity.
-
B.
initialLandingSite
Indicates the location where an entity first arrives, lands, or makes its initial touchdown.
-
C.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another entity.
-
D.
initialGoal
Indicates that something represents the first or starting objective or target in a sequence of goals.
-
E.
initialPosition
chosen
Indicates the original or starting location of an entity before any movement or change in position 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 11:44 a.m.