Triple
T6390199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baoding |
E143804
|
entity |
| Predicate | isFormerMilitaryCenter |
P70331
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Baoding, isFormerMilitaryCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFormerMilitaryCenter Context triple: [Baoding, isFormerMilitaryCenter, true]
-
A.
wasMilitaryHeadquartersOf
Indicates that a place or facility served as the main command center or headquarters for a specific military force or organization.
-
B.
wasMilitaryBaseDuring
Indicates that a location functioned as a military base during a specified time period or event.
-
C.
militaryInstallationType
Indicates the specific category or kind of military installation associated with an entity (e.g., base, fort, airfield, naval station).
-
D.
institutionOfDefense
Indicates that an entity functions as an organization responsible for defense or military protection within a given jurisdiction or context.
-
E.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
- F. None of above. chosen
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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0686cc6d481909c62a29a84a4ce8e |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:34 p.m.