Triple
T37552466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranger-General of Silvermoon |
E933618
|
entity |
| Predicate | isLinkedToLocation |
P185930
|
FINISHED |
| Object | Eversong Woods |
—
|
NE NERFINISHED |
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: Eversong Woods | Statement: [Ranger-General of Silvermoon, isLinkedToLocation, Eversong Woods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinkedToLocation Context triple: [Ranger-General of Silvermoon, isLinkedToLocation, Eversong Woods]
-
A.
linkedLocation
Indicates that one location is associated or connected to another location in a meaningful way, such as being related, referenced, or contextually tied.
-
B.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
C.
connectsLocation
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
-
D.
hasNotableLocationAssociation
chosen
Indicates that there is a significant or noteworthy connection between an entity and a specific location.
-
E.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.