Triple
T38582555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broken Isles |
E932275
|
entity |
| Predicate | centralToFeature |
P197014
|
FINISHED |
| Object | Artifact weapon quests |
—
|
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: Artifact weapon quests | Statement: [Broken Isles, centralToFeature, Artifact weapon quests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralToFeature Context triple: [Broken Isles, centralToFeature, Artifact weapon quests]
-
A.
coordinateReferenceFeature
Indicates that one entity is used as a spatial or positional reference feature for defining the location or geometry of another entity.
-
B.
centralToSeries
Indicates that something is a core or defining element around which a series is organized or structured.
-
C.
centralToArcOf
Indicates that one entity lies at the geometric center or midpoint of an arc defined by another entity.
-
D.
centralToMovement
Indicates that something plays a core, defining, or organizing role within a particular movement or collective effort.
-
E.
centralPointSymbolizes
Indicates that a central point stands for, represents, or embodies a particular concept, value, or meaning within a given context.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
| PDg | Predicate description generation | batch_69fe72db8810819089e397961b8ead7a |
completed | May 8, 2026, 11:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.