Triple
T37150230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-Chain |
E920341
|
entity |
| Predicate | relationToPChain |
P205762
|
FINISHED |
| Object | separate from P-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: separate from P-Chain | Statement: [C-Chain, relationToPChain, separate from P-Chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToPChain Context triple: [C-Chain, relationToPChain, separate from P-Chain]
-
A.
structureRelation
Indicates a structural relationship between entities, specifying how one entity is organized, arranged, or connected in relation to another.
-
B.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
-
C.
relationToSource
Indicates a relationship that specifies how something is connected or related to its originating source.
-
D.
successionRelation
Indicates that one entity follows another in an ordered sequence, such as in time, position, or rank.
-
E.
allyRelation
Indicates a cooperative, supportive relationship in which the entities act as allies toward shared or aligned goals.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:15 p.m.