Triple
T38415761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter Jeep Safari |
E901595
|
entity |
| Predicate | trailExample |
P190857
|
FINISHED |
| Object | Hell’s Revenge |
—
|
NE NERFINISHED |
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: Hell’s Revenge | Statement: [Easter Jeep Safari, trailExample, Hell’s Revenge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailExample Context triple: [Easter Jeep Safari, trailExample, Hell’s Revenge]
-
A.
trackExamples
Indicates that instances or occurrences of something are being monitored, recorded, or kept as examples for reference or analysis.
-
B.
trailEndpoint
Indicates that one entity marks the terminal point or ending location of a trail defined by another entity.
-
C.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
D.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
-
E.
trailUses
Indicates that a trail supports or is designated for specific types of use or activities (such as hiking, biking, or horseback riding).
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.