Triple
T30943170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Knot City |
E788315
|
entity |
| Predicate | hasInGameService |
P199059
|
FINISHED |
| Object | cargo delivery management |
—
|
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: cargo delivery management | Statement: [Lake Knot City, hasInGameService, cargo delivery management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInGameService Context triple: [Lake Knot City, hasInGameService, cargo delivery management]
-
A.
hasInGameActivities
Indicates that an entity includes or offers specific activities or actions that can be performed within a game context.
-
B.
hasInGameCategory
Indicates that an in-game item, action, or entity belongs to a specific predefined category within the game’s classification system.
-
C.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
D.
hasInGameItemType
Indicates that an entity possesses or is associated with a specific type or category of in-game item.
-
E.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
| PDg | Predicate description generation | batch_69ff1d8394988190acf163a07acad200 |
completed | May 9, 2026, 11:41 a.m. |
Created at: April 29, 2026, 8:53 p.m.