Triple
T20391820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tellar Prime |
E498102
|
entity |
| Predicate | preFederationAllegiance |
P43315
|
FINISHED |
| Object | Tellarite planetary government |
—
|
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: Tellarite planetary government | Statement: [Tellar Prime, preFederationAllegiance, Tellarite planetary government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preFederationAllegiance Context triple: [Tellar Prime, preFederationAllegiance, Tellarite planetary government]
-
A.
formerConfederation
Indicates that an entity was previously part of a confederation but is no longer a member.
-
B.
countryOfAllegiance
Indicates the country to which an entity owes loyalty, support, or official allegiance.
-
C.
preConfederationEntity
chosen
Indicates that an entity existed or held a particular status before the formation of a confederation or federal union.
-
D.
allegianceBeforeRule
Indicates that one party’s allegiance or loyalty to another existed prior to the latter’s assumption of rule or authority.
-
E.
hadAllegiance
Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e679108b1481909677cf80e8e77e76 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.