Triple
T24430649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kraang |
E615993
|
entity |
| Predicate | subLeader |
P156095
|
FINISHED |
| Object | Kraang Subprime |
—
|
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: Kraang Subprime | Statement: [Kraang, subLeader, Kraang Subprime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subLeader Context triple: [Kraang, subLeader, Kraang Subprime]
-
A.
secondLeader
Indicates that an entity serves as the second-ranking leader or deputy leader in relation to another entity.
-
B.
establishedUnderLeader
Indicates that an entity was founded, created, or formally established during the tenure or authority of a specific leader.
-
C.
supportedLeader
Indicates that one entity actively backed, endorsed, or provided assistance to a particular leader.
-
D.
laterLeader
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
-
E.
coLeaderWith
Indicates that two or more entities share a joint leadership role or position with equal or comparable authority.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29782a4a0819087cb7ba399371520 |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:16 a.m.