Triple
T30469998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thrill Hill East |
E775264
|
entity |
| Predicate | hasOutboardGear |
P84313
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Thrill Hill East, hasOutboardGear, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutboardGear Context triple: [Thrill Hill East, hasOutboardGear, true]
-
A.
hasRunningGear
Indicates that an entity is equipped with or possesses running gear, such as the mechanical components that enable movement or operation.
-
B.
hasBoat
Indicates that one entity possesses, owns, or has control over a boat.
-
C.
hasArrestingGear
Indicates that an entity is equipped with a system or mechanism used to rapidly decelerate and stop another entity, typically during landing or capture.
-
D.
designedToEmbark
Indicates that something is created or configured with the specific purpose of beginning or initiating a journey, process, or undertaking.
-
E.
hasAuxiliaryEquipment
chosen
Indicates that one entity is equipped with, or accompanied by, additional supporting equipment associated with another entity.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 8:11 p.m.