Triple
T3850961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyline Drive |
E85292
|
entity |
| Predicate | hasNumberOfOverlooks |
P51936
|
FINISHED |
| Object | over 70 |
—
|
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: over 70 | Statement: [Skyline Drive, hasNumberOfOverlooks, over 70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfOverlooks Context triple: [Skyline Drive, hasNumberOfOverlooks, over 70]
-
A.
overlooks
Indicates that one entity has a view toward or looks out over another entity, typically from a higher or adjacent position.
-
B.
hasLookout
Indicates that one entity serves as a lookout or watchful observer for another entity, monitoring for potential events, threats, or changes.
-
C.
overlooksForPromotion
Indicates that an entity responsible for promotions fails to select or consider another entity for advancement despite potential eligibility.
-
D.
oversightType
Indicates the specific kind or category of oversight applied to an entity or activity, such as the manner or level of supervision, review, or regulatory control involved.
-
E.
hasSee
Indicates that one entity has perceived or visually observed another 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcf67788190975105131baabc4b |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:19 p.m.