Triple
T30407199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra Classic |
E773510
|
entity |
| Predicate | previousGovernanceToken |
P195643
|
FINISHED |
| Object | LUNA |
—
|
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: LUNA | Statement: [Terra Classic, previousGovernanceToken, LUNA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousGovernanceToken Context triple: [Terra Classic, previousGovernanceToken, LUNA]
-
A.
governanceToken
Indicates that one entity functions as a governance token for another, conferring rights to participate in decision-making or control over that entity’s governance.
-
B.
previousGoverningBody
Indicates that one governing body served in authority immediately before another specified governing body.
-
C.
governanceRecord
Indicates that there exists a documented governance-related action, decision, or oversight event associated with the entities involved.
-
D.
governanceSeat
Indicates that an entity serves as the official location or seat where another entity’s governance or administrative authority is based or exercised.
-
E.
governanceChange
Indicates a change in the structure, rules, or authority of how an entity, organization, or system is governed.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69fddd364c1481908794c9d423bdc2d7 |
completed | May 8, 2026, 12:55 p.m. |
Created at: April 29, 2026, 8:04 p.m.