Triple
T27470396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xixiabangma |
E693298
|
entity |
| Predicate | isEntirelyWithin |
P50003
|
FINISHED |
| Object | China |
—
|
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: China | Statement: [Xixiabangma, isEntirelyWithin, China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEntirelyWithin Context triple: [Xixiabangma, isEntirelyWithin, China]
-
A.
runsEntirelyWithin
chosen
Indicates that one entity’s spatial or temporal extent is completely contained within the boundaries of another entity, without crossing or exceeding them.
-
B.
regionContains
Indicates that one region spatially encompasses or includes another region within its boundaries.
-
C.
hasBoundaryIncludes
Indicates that the spatial or conceptual boundary of one entity encompasses or contains the boundary of another entity.
-
D.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
E.
isWithinStructure
Indicates that one entity is located inside the physical or logical boundaries of another structure.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e00d1148190bb61a0e1c090a3ff |
completed | May 2, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:53 p.m.