Triple
T35208846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DOMQuad |
E1016614
|
entity |
| Predicate | pointType |
P182612
|
FINISHED |
| Object | DOMPoint |
—
|
NE NERFINISHED |
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: [DOMQuad, pointType, DOMPoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointType Context triple: [DOMQuad, pointType, DOMPoint]
-
A.
pointsType
Indicates that one entity is classified as a specific type or category of points associated with another entity.
-
B.
pointDefinition
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
-
C.
pointSource
Indicates that an entity acts as a localized origin or emitter of some quantity (such as light, sound, or radiation) concentrated at a single point in space.
-
D.
points
Indicates that one entity directs attention, focus, or a physical/abstract indication toward another entity or location.
-
E.
KPoint
Indicates a relationship where a specific point is designated or identified as a key or reference point within a spatial or geometric context.
- 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.