Triple
T26489734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Møllehøj |
E669122
|
entity |
| Predicate | hasManMadeStructureNearby |
P124983
|
FINISHED |
| Object | Ejer Bavnehøj tower |
—
|
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: Ejer Bavnehøj tower | Statement: [Møllehøj, hasManMadeStructureNearby, Ejer Bavnehøj tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManMadeStructureNearby Context triple: [Møllehøj, hasManMadeStructureNearby, Ejer Bavnehøj tower]
-
A.
isMostDistantHumanMadeObject
Indicates that the subject is the human-made object currently farthest from Earth (or from its point of origin).
-
B.
hasNearbyRiverStructure
Indicates that a river-related structure (such as a dam, bridge, or levee) is located close to the referenced entity.
-
C.
hasNearbyInfrastructureType
chosen
Indicates that an entity is located close to infrastructure of a specified type.
-
D.
builtNear
Indicates that one entity was constructed at a location geographically close to another entity.
-
E.
hasMainBuildingNear
Indicates that the primary or central building associated with an entity is located in close physical proximity to another specified entity or place.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 27, 2026, 1:02 a.m.