Triple
T29526427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NQY |
E749081
|
entity |
| Predicate | spaceportFacility |
P80788
|
FINISHED |
| Object | Spaceport Cornwall |
—
|
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: Spaceport Cornwall | Statement: [NQY, spaceportFacility, Spaceport Cornwall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceportFacility Context triple: [NQY, spaceportFacility, Spaceport Cornwall]
-
A.
spaceportLocation
Indicates the place where a spaceport is situated or hosted.
-
B.
spaceportServed
Indicates that a spaceport provides service or access to a particular location, route, or entity (such as a city, region, or transport network).
-
C.
spaceportState
Indicates the operational or regulatory status currently assigned to a spaceport.
-
D.
spaceportRole
chosen
Indicates the functional role or capacity an entity has in relation to a spaceport (e.g., operator, facility type, or service function).
-
E.
spaceportUsedWith
Indicates that a spaceport is utilized in conjunction with a particular vehicle, mission, or operation for launch, landing, or related spaceflight activities.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 4:46 p.m.