Triple
T26408822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xoodoo |
E663901
|
entity |
| Predicate | hasBlockStructure |
P158692
|
FINISHED |
| Object | 3D state array |
—
|
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: 3D state array | Statement: [Xoodoo, hasBlockStructure, 3D state array]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBlockStructure Context triple: [Xoodoo, hasBlockStructure, 3D state array]
-
A.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
B.
hasChunkStructure
chosen
Indicates that an entity is composed of distinct chunks or segments arranged in a specific structural organization.
-
C.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
D.
hasLineStructure
Indicates that one entity possesses or exhibits a linear arrangement or organization of its components.
-
E.
hasLogicalStructure
Indicates that one entity possesses or exhibits a specific underlying logical organization or pattern defined by another entity.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610faa77081908956b6e8b5b1570c |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:36 p.m.