Triple
T27291815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ksar Sghir |
E688647
|
entity |
| Predicate | nearbyCountryAcrossStrait |
P169892
|
FINISHED |
| Object | Spain |
—
|
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: Spain | Statement: [Ksar Sghir, nearbyCountryAcrossStrait, Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCountryAcrossStrait Context triple: [Ksar Sghir, nearbyCountryAcrossStrait, Spain]
-
A.
oppositeCityAcrossStrait
Indicates that one city is located directly across a strait from another city, facing it on the opposite shore.
-
B.
nearbyMainlandArea
chosen
Indicates that one area is located close to or adjacent to a mainland area.
-
C.
isPartOfCrossStraitRelations
Indicates that something belongs to, affects, or is involved in the political, economic, social, or cultural interactions and dynamics between the two sides of the Taiwan Strait.
-
D.
positionOnCrossStraitRelations
Indicates a stance or viewpoint an entity holds regarding political, economic, or diplomatic relations between the two sides of the Taiwan Strait.
-
E.
distanceFromTaiwanMainIsland
Indicates the measured spatial distance between an entity’s location and the main island of Taiwan.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 27, 2026, 11:16 a.m.