Triple
T37553394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valley of Spirits zeppelin tower |
E933639
|
entity |
| Predicate | travelCost |
P115145
|
FINISHED |
| Object | free in-game travel |
—
|
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: free in-game travel | Statement: [Valley of Spirits zeppelin tower, travelCost, free in-game travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelCost Context triple: [Valley of Spirits zeppelin tower, travelCost, free in-game travel]
-
A.
fareCalculation
Indicates the process or method used to determine the monetary cost of a trip or service based on specified pricing rules and conditions.
-
B.
travelMechanic
Indicates the method or system by which movement or travel between locations is carried out.
-
C.
economicCost
chosen
Indicates the financial burden, expense, or resource expenditure associated with an action, event, or relationship between entities.
-
D.
travelAllowance
Indicates that an entity is entitled to or receives a monetary allowance specifically for travel-related expenses.
-
E.
estimatedCost
Indicates the predicted or calculated monetary amount expected to be required for something, such as a project, item, or action.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:17 p.m.