Triple
T23114089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Observatoire Royal de Belgique |
E576400
|
entity |
| Predicate | hasCoordinateSystemWork |
P2054
|
FINISHED |
| Object | reference frames |
—
|
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: reference frames | Statement: [Observatoire Royal de Belgique, hasCoordinateSystemWork, reference frames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoordinateSystemWork Context triple: [Observatoire Royal de Belgique, hasCoordinateSystemWork, reference frames]
-
A.
hasProjectionSystem
Indicates that one entity uses or is defined by a particular coordinate or map projection system associated with another entity.
-
B.
hasCoordinateProcess
Indicates that two or more processes occur in parallel or in coordination, sharing a similar role or function within a broader context.
-
C.
usesCoordinateRepresentation
Indicates that one entity expresses or handles another entity in terms of a specific coordinate-based representation.
-
D.
coordinateSystem
chosen
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
E.
hasCoordinates
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e1121c08190a1d29fe594071c46 |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:59 p.m.