Triple
T4293684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A3C |
E99656
|
entity |
| Predicate | handlesInputType |
P11909
|
FINISHED |
| Object | high-dimensional sensory input |
—
|
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: high-dimensional sensory input | Statement: [A3C, handlesInputType, high-dimensional sensory input]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesInputType Context triple: [A3C, handlesInputType, high-dimensional sensory input]
-
A.
hasInputType
Indicates that an entity takes another entity as its input type for its operation, function, or process.
-
B.
inputType
chosen
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
C.
hasInput
Indicates that an entity receives or takes another entity as an input to its process, function, or operation.
-
D.
hasHandleType
Indicates that one entity possesses or is characterized by a specific type or style of handle.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35082228081908504e3fd7c4ca1e8 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.