Triple
T15533206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Beerburrum |
E370273
|
entity |
| Predicate | hasLookoutStructure |
P119049
|
FINISHED |
| Object | concrete tower |
—
|
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: concrete tower | Statement: [Mount Beerburrum, hasLookoutStructure, concrete tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLookoutStructure Context triple: [Mount Beerburrum, hasLookoutStructure, concrete tower]
-
A.
hasLookout
Indicates that one entity serves as a lookout or watchful observer for another entity, monitoring for potential events, threats, or changes.
-
B.
hasObservationStructure
Indicates that an entity is associated with, or organized according to, a specific structure or schema used for recording or representing observations.
-
C.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
D.
hasObservationArea
Indicates that an entity possesses or includes a designated area from which observations or monitoring activities are conducted.
-
E.
hasNumberOfOverlooks
Indicates the specific count of overlooks (such as viewing points or vantage spots) associated with an entity.
- F. None of above. chosen
Provenance (4 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414877d88190804ee76566004e13 |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:06 a.m.