Triple
T30345579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unlimited Blade Works route |
E771859
|
entity |
| Predicate | orderInGame |
P166584
|
FINISHED |
| Object | second main route |
—
|
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: second main route | Statement: [Unlimited Blade Works route, orderInGame, second main route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderInGame Context triple: [Unlimited Blade Works route, orderInGame, second main route]
-
A.
orderWithin
Indicates that one entity is positioned or ranked before or after another entity within a defined sequence or ordering.
-
B.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
C.
order
Indicates that one entity requests, arranges, or directs that another entity provide a good, service, or action, typically in a specified sequence or priority.
-
D.
isOrderIn
Indicates that one entity is contained within or belongs to a specified order or sequence of entities.
-
E.
positionOnOrder
chosen
Indicates the specific placement or sequence of an item within an ordered list or collection.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 29, 2026, 7:55 p.m.