Triple
T27848758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weiming clan |
E703893
|
entity |
| Predicate | geopoliticalNeighbors |
P163736
|
FINISHED |
| Object | Liao dynasty |
—
|
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: Liao dynasty | Statement: [Weiming clan, geopoliticalNeighbors, Liao dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geopoliticalNeighbors Context triple: [Weiming clan, geopoliticalNeighbors, Liao dynasty]
-
A.
geopoliticalNeighbors
chosen
Indicates that two geopolitical entities share a common border or are directly adjacent to each other territorially.
-
B.
geographicNeighbors
Indicates that two geographic entities share a common boundary or are directly adjacent to each other in space.
-
C.
borderingCountryNearby
Indicates that one country is geographically close to, but does not necessarily share a direct land border with, another country.
-
D.
neighboringCountryBySea
Indicates that one country is adjacent to another with their territories touching via a shared sea boundary rather than solely by land.
-
E.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:09 p.m.