Triple
T27122507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nearctic |
E687038
|
entity |
| Predicate | pairedWithRealm |
P48425
|
FINISHED |
| Object | Palearctic realm |
—
|
NE NERFINISHED |
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: Palearctic realm | Statement: [Nearctic, pairedWithRealm, Palearctic realm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairedWithRealm Context triple: [Nearctic, pairedWithRealm, Palearctic realm]
-
A.
associatedWithRealm
chosen
Indicates a relationship where an entity is linked or connected to a particular realm, domain, or sphere of influence.
-
B.
pairedWithRelationshipName
Indicates that one entity is associated with another as a named pair within a specific relationship context.
-
C.
pairedWithFunctionally
Indicates that one entity is functionally matched or coupled with another to perform a complementary or corresponding role.
-
D.
pairedSingleWith
Indicates that one entity is matched or associated as a single counterpart with another single entity, typically forming an exclusive one-to-one pairing.
-
E.
spouseRealm
Indicates that two entities are spouses within, or in relation to, a particular realm, jurisdiction, or domain.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f624454be48190908449be1be4d1a4 |
completed | May 2, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9 a.m.