Triple
T4727572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heron Tower |
E104922
|
entity |
| Predicate | hasObservationAreas |
P50321
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Heron Tower, hasObservationAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObservationAreas Context triple: [Heron Tower, hasObservationAreas, yes]
-
A.
hasObservationArea
chosen
Indicates that an entity possesses or includes a designated area from which observations or monitoring activities are conducted.
-
B.
hasObservationSite
Indicates that something (such as a measurement, event, or observation activity) is associated with or took place at a specific observation site or location.
-
C.
hasObservationFacility
Indicates that an entity possesses or is associated with a facility used for observing, monitoring, or collecting data about something.
-
D.
hasAreaOfInterest
Indicates that an entity possesses or is associated with a particular area of interest or focus.
-
E.
hasObservation
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
- 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_69bd43ed84648190ae0b7ee8e8d00482 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.