Triple
T29638290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GTA-9A |
E755784
|
entity |
| Predicate | crewCallsigned |
P1565
|
FINISHED |
| Object | Gemini 9A |
—
|
NE NERFINISHED |
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: Gemini 9A | Statement: [GTA-9A, crewCallsigned, Gemini 9A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewCallsigned Context triple: [GTA-9A, crewCallsigned, Gemini 9A]
-
A.
supportsCallSign
Indicates that one entity is capable of recognizing, handling, or operating using a specified call sign.
-
B.
callsign
chosen
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
C.
formerCallSign
Indicates that one identifier was previously used as the call sign for the other entity before being changed or replaced.
-
D.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
E.
inspiredCallsignOf
Indicates that one entity’s callsign was created based on, influenced by, or derived from 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66ecb9c348190ad7a99d6ea5920d8 |
completed | May 2, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:45 p.m.