Triple
T32043802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milne universe model |
E818283
|
entity |
| Predicate | usesCoordinates |
P131273
|
FINISHED |
| Object | Milne coordinates |
—
|
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: Milne coordinates | Statement: [Milne universe model, usesCoordinates, Milne coordinates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCoordinates Context triple: [Milne universe model, usesCoordinates, Milne coordinates]
-
A.
hasCoordinates
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
B.
coordinatesIn
Indicates that one entity specifies the spatial coordinates or position of another entity within a given reference frame or system.
-
C.
usesCoordinateReference
chosen
Indicates that one entity adopts or relies on the coordinate reference system defined or provided by another entity.
-
D.
coordinatesUseOf
Indicates that one entity organizes and manages the collaborative use or deployment of another entity’s resources, actions, or functions.
-
E.
coordinatesWith
Indicates that one entity works together with another in an organized or synchronized manner to achieve a shared or compatible outcome.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 12:19 a.m.