Triple
T839555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartbreak Hill |
E18145
|
entity |
| Predicate | spectatorPresence |
P13931
|
FINISHED |
| Object | large crowds |
—
|
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: large crowds | Statement: [Heartbreak Hill, spectatorPresence, large crowds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectatorPresence Context triple: [Heartbreak Hill, spectatorPresence, large crowds]
-
A.
hasSpectatorArea
Indicates that a location or facility includes a designated area intended for spectators to observe an event or activity.
-
B.
globalPresence
Indicates that an entity operates, is represented, or has a significant footprint across multiple countries or world regions.
-
C.
hasHumanPresence
chosen
Indicates that humans are physically present in or occupying a given location, object, or context.
-
D.
onlinePresence
Indicates that an entity maintains a presence or representation on the internet, such as through websites, profiles, or digital platforms.
-
E.
hasLargePresenceIn
Indicates that an entity maintains a significant or dominant level of activity, influence, or representation within a specified location, domain, or context.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abe4ab1081909207ae2eec1898d9 |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7dfc5c8190890c9df485d73a86 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.