Triple
T37552321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broken Isles Pathfinder, Part Two |
E933615
|
entity |
| Predicate | affectsTravel |
P189059
|
FINISHED |
| Object | mount usage in Broken Isles |
—
|
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: mount usage in Broken Isles | Statement: [Broken Isles Pathfinder, Part Two, affectsTravel, mount usage in Broken Isles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsTravel Context triple: [Broken Isles Pathfinder, Part Two, affectsTravel, mount usage in Broken Isles]
-
A.
travelsFor
Indicates that one entity moves from place to place on behalf of, or for the benefit or purpose of, another entity or objective.
-
B.
travelsOn
Indicates that an entity moves or journeys using a particular route, path, or mode of transportation.
-
C.
coTraveler
Indicates that two or more entities are traveling together along (part of) the same journey or route.
-
D.
involvedTravelBetween
Indicates a relationship where an entity participates in or is associated with travel occurring between two specified locations.
-
E.
basedOnTravel
Indicates that something is determined, derived, or decided according to travel-related factors, conditions, or information.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.