Triple
T37514860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grinding Gear Games |
E932608
|
entity |
| Predicate | hasFeatureInPathOfExile |
P182
|
FINISHED |
| Object | league-specific mechanics |
—
|
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: league-specific mechanics | Statement: [Grinding Gear Games, hasFeatureInPathOfExile, league-specific mechanics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeatureInPathOfExile Context triple: [Grinding Gear Games, hasFeatureInPathOfExile, league-specific mechanics]
-
A.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
B.
hasInUniversePublicFeature
Indicates that an entity possesses a public-facing feature or characteristic within a specific fictional or defined universe.
-
C.
hasTempleFeature
Indicates that an entity possesses a specific architectural or structural feature characteristic of a temple.
-
D.
hasCastleFeature
Indicates that an entity possesses or includes a specific architectural or structural feature of a castle.
-
E.
hasDiscoveryFeature
Indicates that an entity includes or supports a capability for discovering, finding, or surfacing other relevant entities, items, or information.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.