Triple
T37068678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chimor |
E917517
|
entity |
| Predicate | expandedAlong |
P126671
|
FINISHED |
| Object | Pacific coast of northern Peru |
—
|
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: Pacific coast of northern Peru | Statement: [Chimor, expandedAlong, Pacific coast of northern Peru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedAlong Context triple: [Chimor, expandedAlong, Pacific coast of northern Peru]
-
A.
expansionAlongside
Indicates that one entity expands or grows in parallel with, and in relation to, the expansion of another entity.
-
B.
expandedAcross
Indicates that something has grown or extended so that it now spans or covers multiple areas, regions, or segments.
-
C.
expandedAs
Indicates that one entity is a more detailed, elaborated, or fully written-out form of another, capturing how the latter is expanded from the former.
-
D.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
E.
extendedTowards
chosen
Indicates that one entity is stretched or directed outward in the direction of another entity or location.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:14 p.m.