Triple
T38675560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRP Sierra Madre |
E943729
|
entity |
| Predicate | locatedInDisputedBy |
P15542
|
FINISHED |
| Object | China |
E5561
|
NE 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: China | Statement: [BRP Sierra Madre, locatedInDisputedBy, China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDisputedBy Context triple: [BRP Sierra Madre, locatedInDisputedBy, China]
-
A.
locatedInDisputedTerritory
chosen
Indicates that an entity is situated within a geographic area whose sovereignty or ownership is contested between two or more parties.
-
B.
locatedOnSideOfConflict
Indicates that an entity is positioned or aligned on a particular side or faction within a conflict.
-
C.
nearbyDisputedArea
Indicates that an entity is located close to a geographic area whose ownership, control, or boundaries are contested.
-
D.
associatedTerritoryDispute
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
E.
locationDuringConflict
Indicates that an entity is situated in a specific place for some or all of the duration of a particular conflict or hostilities.
- F. None of above.
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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd4ae44881908363c1826e586564 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.