Triple
T26519393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billefjorden |
E669909
|
entity |
| Predicate | hasNearbyAbandonedSettlement |
P91545
|
FINISHED |
| Object | Pyramiden |
—
|
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: Pyramiden | Statement: [Billefjorden, hasNearbyAbandonedSettlement, Pyramiden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyAbandonedSettlement Context triple: [Billefjorden, hasNearbyAbandonedSettlement, Pyramiden]
-
A.
hasNearbyGhostTown
chosen
Indicates that one location is situated close to a ghost town, i.e., an abandoned or nearly abandoned settlement.
-
B.
hasNearbyTown
Indicates that one location has a town situated close to it in geographic proximity.
-
C.
hasNearbyColony
Indicates that one entity has another entity located close enough to be considered a nearby colony.
-
D.
hasNearbyTribalLand
Indicates that an entity is located close to or adjacent to land officially recognized as belonging to a tribal nation or indigenous community.
-
E.
hasTribalHeadquartersNearby
Indicates that the subject entity is located close to the tribal headquarters of a Native nation or tribe.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 1:26 a.m.