Triple
T21123782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manned Orbiting Laboratory |
E520497
|
entity |
| Predicate | numberOfOperationalFlights |
P4899
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Manned Orbiting Laboratory, numberOfOperationalFlights, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfOperationalFlights Context triple: [Manned Orbiting Laboratory, numberOfOperationalFlights, 0]
-
A.
numberOfFlights
chosen
Indicates the total count of flights associated with a given entity or within a specified context.
-
B.
airlineOperationsType
Indicates the type or category of operational activities an airline conducts (e.g., passenger, cargo, charter, or mixed services).
-
C.
quantityFlown
Indicates the amount or volume that has been transported by flying from one place to another.
-
D.
numberOfCaptiveFlights
Indicates the number of flights during which an entity is held or transported in captivity.
-
E.
operationalControlOfFlights
Indicates that one entity has the authority and responsibility to manage and direct the operation of specific flights conducted by another entity.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72236b2d88190bef9f0cd6924ca92 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:55 p.m.