Triple
T16933799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intelsat |
E410778
|
entity |
| Predicate | formerLegalForm |
P42670
|
FINISHED |
| Object | intergovernmental organization |
—
|
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: intergovernmental organization | Statement: [Intelsat, formerLegalForm, intergovernmental organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerLegalForm Context triple: [Intelsat, formerLegalForm, intergovernmental organization]
-
A.
previousLegalForm
chosen
Indicates the legal form or organizational status an entity had before its current legal form.
-
B.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
C.
typicalLegalForm
Indicates the standard or commonly used legal organizational form associated with an entity.
-
D.
formerLegalRestriction
Indicates that a legal restriction once applied to an entity or relationship but is no longer in effect.
-
E.
legalFormedAs
Indicates that an entity was established or constituted under a specific legal structure or organizational form.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2714b08190a2524d5d9578cc87 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.