Triple
T37661619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End Barrens |
E937728
|
entity |
| Predicate | canBeMappedWith |
P89549
|
FINISHED |
| Object | locator map |
—
|
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: locator map | Statement: [End Barrens, canBeMappedWith, locator map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeMappedWith Context triple: [End Barrens, canBeMappedWith, locator map]
-
A.
canBeImplementedWith
Indicates that one entity is capable of being realized, executed, or fulfilled through the use or application of another entity.
-
B.
canBeDefinedFor
Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
-
C.
canBeLinkedTo
Indicates that one entity has the potential or capability to be connected or associated with another entity.
-
D.
canBeConstructedWith
Indicates that one entity can be formed, built, or assembled using another entity as material, components, or means.
-
E.
hasOfficialMapping
chosen
Indicates that there exists an established, authoritative correspondence or translation between one entity and another.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 3, 2026, 4:18 p.m.