Triple
T37513132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary |
E932564
|
entity |
| Predicate | historyInfluencedBy |
P87217
|
FINISHED |
| Object | Worldstone |
E932552
|
NE 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: Worldstone | Statement: [Sanctuary, historyInfluencedBy, Worldstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historyInfluencedBy Context triple: [Sanctuary, historyInfluencedBy, Worldstone]
-
A.
hasHistoricalInfluenceFrom
Indicates that one entity’s characteristics, development, or significance have been shaped or affected by the past actions, ideas, or legacy of another entity.
-
B.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
C.
wereInfluencedBy
chosen
Indicates that one entity’s ideas, actions, or characteristics were shaped or affected by another entity.
-
D.
hasHistoricalWritingInfluenceFrom
Indicates that one entity’s historical writing style, content, or traditions are influenced by those of another entity.
-
E.
hadInfluenceOn
Indicates that one entity affected, shaped, or contributed to the development, behavior, or characteristics of another entity.
- F. None of above.
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_6a01a48fbbd481908ccf75551dcf4647 |
completed | May 11, 2026, 9:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40d6640c408190b17cfe2fae20c95c |
completed | June 28, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_6a01a2d6db208190b11c1af601a544f5 |
completed | May 11, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:17 p.m.