Triple
T30407217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra Classic |
E773510
|
entity |
| Predicate | statusAfterFork |
P194946
|
FINISHED |
| Object | legacy chain |
—
|
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: legacy chain | Statement: [Terra Classic, statusAfterFork, legacy chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterFork Context triple: [Terra Classic, statusAfterFork, legacy chain]
-
A.
statusInSuccession
Indicates the position or rank an individual holds within an established line of succession to a title, role, or office.
-
B.
statusAfterRelocation
Indicates the condition or state an entity has once it has been moved from its original location to a new one.
-
C.
statusAfterSupersession
Indicates the status or condition an entity holds after it has been superseded by another entity.
-
D.
statusAfterLeak
Indicates the condition or state of an entity after a leak event has occurred.
-
E.
statusAfterUnification
Indicates the resulting status or condition of an entity after a unification process or merging event has occurred.
- 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_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
| PDg | Predicate description generation | batch_69fd91a44268819081b372296e3aa116 |
completed | May 8, 2026, 7:32 a.m. |
Created at: April 29, 2026, 8:04 p.m.