Triple
T14542508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US-2 |
E341203
|
entity |
| Predicate | roleClassification |
P102097
|
FINISHED |
| Object | special-mission aircraft |
—
|
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: special-mission aircraft | Statement: [US-2, roleClassification, special-mission aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleClassification Context triple: [US-2, roleClassification, special-mission aircraft]
-
A.
classificationRole
chosen
Indicates that one entity serves as a classificatory role or type used to categorize or group another entity.
-
B.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
-
C.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
D.
designationCategory
Indicates the classification or type of designation assigned to an entity within a broader designation system.
-
E.
roleInGemini10
Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1be5a8081909bf727e28a5bba4a |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.