Triple
T16743634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communications Satellite Corporation |
E406893
|
entity |
| Predicate | roleInIntelsat |
P67302
|
FINISHED |
| Object | U.S. signatory to Intelsat |
—
|
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: U.S. signatory to Intelsat | Statement: [Communications Satellite Corporation, roleInIntelsat, U.S. signatory to Intelsat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInIntelsat Context triple: [Communications Satellite Corporation, roleInIntelsat, U.S. signatory to Intelsat]
-
A.
roleInISRO
Indicates that an entity holds or has held a specific role, position, or responsibility within the Indian Space Research Organisation (ISRO).
-
B.
roleInSpaceX
Indicates that one entity holds or has held a specific role, position, or function within the organization SpaceX.
-
C.
roleAtSiebelSystems
Indicates that an entity held a specific role or position at Siebel Systems.
-
D.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
-
E.
hasTelecommunicationsRole
chosen
Indicates that an entity holds or performs a specific function, position, or responsibility within the field of telecommunications.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa205138819080284fd9a4341225 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.