Triple
T27122480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nearctic |
E687038
|
entity |
| Predicate | separatedFromRealmBy |
P162507
|
FINISHED |
| Object | tropical regions of Mexico |
—
|
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: tropical regions of Mexico | Statement: [Nearctic, separatedFromRealmBy, tropical regions of Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatedFromRealmBy Context triple: [Nearctic, separatedFromRealmBy, tropical regions of Mexico]
-
A.
laterSeparatedFrom
Indicates that one entity became separated from another at a later time than some referenced separation event.
-
B.
separatedFromSerialBy
Indicates that one entity is positioned with a serial element (such as a serial number or serial identifier) acting as a separator between it and another entity.
-
C.
associatedWithRealm
Indicates a relationship where an entity is linked or connected to a particular realm, domain, or sphere of influence.
-
D.
separatedUntil
Indicates that two entities remain apart or not in contact up to a specified time or condition.
-
E.
createdBySeparationFrom
Indicates that one entity comes into existence as a result of being separated or split off from another entity.
- F. None of above. chosen
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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f625402d808190be8279d895d2b27f |
completed | May 2, 2026, 4:24 p.m. |
Created at: April 27, 2026, 9 a.m.