Triple
T1038380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American crocodile |
E22414
|
entity |
| Predicate | rangeLimitSouth |
P13333
|
FINISHED |
| Object | 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: northern Peru | Statement: [American crocodile, rangeLimitSouth, northern Peru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeLimitSouth Context triple: [American crocodile, rangeLimitSouth, northern Peru]
-
A.
southernBoundaryReference
chosen
Indicates that one entity is used as the reference or defining limit for the southern boundary of another entity.
-
B.
locatedSouthOf
Indicates that one entity is positioned geographically to the south of another entity.
-
C.
jurisdictionLimit
Indicates the maximum scope or boundary within which an authority, organization, or rule is legally empowered to operate or exercise control.
-
D.
locatedSouthWestOf
Indicates that one entity is positioned to the southwest of another entity, combining both a southern and western relative location.
-
E.
isSouthernmostLatitudeWhereSunCanBeOverhead
Indicates the southernmost latitude on Earth at which the Sun can appear directly overhead (at the zenith) at some time during the year.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.