Triple
T37471643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirnenn |
E931167
|
entity |
| Predicate | associatedWithZone |
P121877
|
FINISHED |
| Object | Ardenweald |
E273804
|
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: Ardenweald | Statement: [Tirnenn, associatedWithZone, Ardenweald]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithZone Context triple: [Tirnenn, associatedWithZone, Ardenweald]
-
A.
associatedWithFaultZone
Indicates that one entity has a spatial, structural, or causal relationship with a geological fault zone.
-
B.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
C.
associatedWithCluster
Indicates that an entity is linked or grouped with a particular cluster, typically sharing common characteristics or membership within that cluster.
-
D.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
E.
linkedToCanonicalZone
chosen
Indicates that an entity is associated with or mapped to its corresponding canonical (standardized) zone.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40f165a28881909262db8241bb7032 |
completed | June 28, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.