Triple
T35208900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOMPoint |
E1016615
|
entity |
| Predicate | returnsFromMatrixTransform |
P78038
|
FINISHED |
| Object | DOMPoint |
—
|
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: DOMPoint | Statement: [DOMPoint, returnsFromMatrixTransform, DOMPoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnsFromMatrixTransform Context triple: [DOMPoint, returnsFromMatrixTransform, DOMPoint]
-
A.
inverseTransform
Indicates that one entity represents the inverse operation or mapping that undoes the transformation performed by another entity.
-
B.
coordinateTransformation
Indicates a relationship where one coordinate system is mathematically converted or mapped into another, preserving the correspondence of points between them.
-
C.
transformationResult
chosen
Indicates that one entity is the output or outcome produced by applying a transformation process to another entity.
-
D.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
E.
regionTransformed
Indicates that one region has been changed or converted into another region through some transformation process.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:02 p.m.