Triple
T35208917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOMPoint |
E1016615
|
entity |
| Predicate | wRepresents |
P182616
|
FINISHED |
| Object | homogeneous coordinate |
—
|
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: homogeneous coordinate | Statement: [DOMPoint, wRepresents, homogeneous coordinate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wRepresents Context triple: [DOMPoint, wRepresents, homogeneous coordinate]
-
A.
winnerRepresents
Indicates that the winner of a competition or contest serves as a representative for a particular group, organization, or entity.
-
B.
representationIn
Indicates that one entity serves as a depiction, model, or stand-in for another entity within a given context or medium.
-
C.
rimRepresents
Indicates that one entity serves as a representation, model, or stand-in for another entity within a specific context or system.
-
D.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
E.
resents
Indicates that one entity feels bitterness, anger, or lingering ill will toward another, typically due to a perceived wrong or unfair treatment.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.