Triple
T10211963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan IV |
E242349
|
entity |
| Predicate | notablePayloadType |
P39951
|
FINISHED |
| Object | reconnaissance satellites |
—
|
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: reconnaissance satellites | Statement: [Titan IV, notablePayloadType, reconnaissance satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePayloadType Context triple: [Titan IV, notablePayloadType, reconnaissance satellites]
-
A.
notableContentType
Indicates the type or category of content for which an entity is notable or best known.
-
B.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
C.
notableCargo
chosen
Indicates that an entity is known for carrying or having carried a particularly important, famous, or otherwise noteworthy cargo.
-
D.
notableRecipientType
Indicates that an entity is notably recognized as a recipient of something (such as an award, honor, or distinction) of a specified type.
-
E.
notableOperationType
Indicates that an entity is associated with a specific type or category of operation that is considered notable or significant.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa23bce881909b5deac612ec22cb |
completed | April 6, 2026, 12:42 p.m. |
| PD | Predicate disambiguation | batch_69d39559e5ac8190b88eca75956b7e6a |
completed | April 6, 2026, 11:13 a.m. |
Created at: April 6, 2026, 11:02 a.m.