Triple
T7921624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobi matrix |
E183956
|
entity |
| Predicate | isOperatorOn |
P79799
|
FINISHED |
| Object | ℓ²(ℕ) in infinite-dimensional case |
—
|
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: ℓ²(ℕ) in infinite-dimensional case | Statement: [Jacobi matrix, isOperatorOn, ℓ²(ℕ) in infinite-dimensional case]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOperatorOn Context triple: [Jacobi matrix, isOperatorOn, ℓ²(ℕ) in infinite-dimensional case]
-
A.
involvesOperator
Indicates that a given process, action, or relationship includes or makes use of a specific operator as a participating element.
-
B.
isOperatedIn
Indicates that an entity carries out its operations or activities within a specified location, region, or jurisdiction.
-
C.
typicalOperatorType
Indicates the usual or most common type or category of operator associated with a given entity or context.
-
D.
operatorBase
Indicates that one entity serves as the primary or foundational operator for another entity or operation.
-
E.
usedByOperator
Indicates that something is utilized or operated by a particular operator or operating entity.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a9499cc8190b6bd81f4625c77ab |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:06 p.m.