Triple
T32668583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed Agena upper stage |
E835227
|
entity |
| Predicate | roleInGeminiProgram |
P202034
|
FINISHED |
| Object | target vehicle for orbital rendezvous |
—
|
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: target vehicle for orbital rendezvous | Statement: [Lockheed Agena upper stage, roleInGeminiProgram, target vehicle for orbital rendezvous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInGeminiProgram Context triple: [Lockheed Agena upper stage, roleInGeminiProgram, target vehicle for orbital rendezvous]
-
A.
roleInGemini3
Indicates that an entity holds a specific role or function within the Gemini 3 mission or project.
-
B.
roleInGemini10
Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
-
C.
roleAtAnthropic
Indicates that an entity holds or held a specific role or position at Anthropic.
-
D.
roleOfPerson
Indicates that a specific role, function, or position is assigned to or held by a particular person.
-
E.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
| PDg | Predicate description generation | batch_6a004868cf308190a2a93c32c92f22d9 |
completed | May 10, 2026, 8:57 a.m. |
Created at: May 1, 2026, 1:08 a.m.