Triple
T17626590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jundu Mountains |
E429859
|
entity |
| Predicate | historicallyProtected |
P79175
|
FINISHED |
| Object | Chinese capital |
—
|
LITERAL 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: Chinese capital | Statement: [Jundu Mountains, historicallyProtected, Chinese capital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyProtected Context triple: [Jundu Mountains, historicallyProtected, Chinese capital]
-
A.
historicallyGuardedBy
chosen
Indicates that an entity was protected or defended by another entity during a past historical period.
-
B.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
-
C.
historicallyKeptAt
Indicates that an entity was stored or maintained at a particular location during a past period of time.
-
D.
historicallyEncompassed
Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
-
E.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbd122c8190a5db8c0088c81034 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.