Triple
T4390970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theano |
E99360
|
entity |
| Predicate | supportsDataStructure |
P32204
|
FINISHED |
| Object | multi-dimensional arrays |
—
|
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: multi-dimensional arrays | Statement: [Theano, supportsDataStructure, multi-dimensional arrays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDataStructure Context triple: [Theano, supportsDataStructure, multi-dimensional arrays]
-
A.
supportsStructure
Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
-
B.
usesDataStructure
chosen
Indicates that one entity employs or relies on a particular data structure in its operation or implementation.
-
C.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportStructureFor
Indicates that one entity serves as a physical or functional support structure for another entity.
-
E.
storageStructure
Indicates a relationship where one entity serves as a physical or logical structure used to store or contain 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352843d7c8190929b94c94eaa63df |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.