Triple
T37514967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marauder (Path of Exile) |
E932610
|
entity |
| Predicate | typicalBuilds |
P205946
|
FINISHED |
| Object | heavy armour melee builds |
—
|
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: heavy armour melee builds | Statement: [Marauder (Path of Exile), typicalBuilds, heavy armour melee builds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBuilds Context triple: [Marauder (Path of Exile), typicalBuilds, heavy armour melee builds]
-
A.
builtType
Indicates the structural or construction type characterizing how something is built or formed.
-
B.
averageBuild
Indicates that an entity has a body type or physical build that is of medium or typical size, neither notably small nor large.
-
C.
buildableBy
Indicates that something can be constructed, created, or assembled by a specified agent or entity.
-
D.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
E.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.