Triple
T23618747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury-Atlas 5 |
E583252
|
entity |
| Predicate | numberOfOrbitsPlanned |
P153289
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Mercury-Atlas 5, numberOfOrbitsPlanned, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfOrbitsPlanned Context triple: [Mercury-Atlas 5, numberOfOrbitsPlanned, 3]
-
A.
numberOfOrbitalPlanes
Indicates the specific count of distinct orbital planes associated with an object or system.
-
B.
orbitsUsed
Indicates that one entity utilizes or traverses specific orbital paths associated with another entity.
-
C.
originalPlannedOrbit
Indicates the initially intended or designed orbital path or parameters for an object before any changes or deviations occurred.
-
D.
numberOfGEOSatellitesPlanned
Indicates the planned quantity of GEO (geostationary) satellites associated with a given entity or mission.
-
E.
orbitsCovered
Indicates that one entity completes or spans a specified number of orbital revolutions around another entity.
- 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_69e248fbcd9081908ba08913f9d30826 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b176751c8190aee7746a2f1f15d5 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f138b8c9248190b059bc38a9a50958 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 17, 2026, 6:45 p.m.