Triple
T33566953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GRS80 |
E859784
|
entity |
| Predicate | datumRole |
P108488
|
FINISHED |
| Object | ellipsoid for global reference systems |
—
|
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: ellipsoid for global reference systems | Statement: [GRS80, datumRole, ellipsoid for global reference systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datumRole Context triple: [GRS80, datumRole, ellipsoid for global reference systems]
-
A.
notationRole
Indicates a role or function that an entity plays specifically within a system of notation or symbolic representation.
-
B.
conceptualRole
Indicates the functional or semantic role that one concept plays in relation to another within a conceptual structure or system.
-
C.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
D.
roleInMetadata
chosen
Indicates that an entity serves a specific function or position within a metadata record or metadata structure.
-
E.
basisRole
Indicates that one role serves as the foundational or underlying role upon which another role or function is defined or derived.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f740ee548190a73daee3321d8264 |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.