Triple
T38675809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nansha Qundao |
E943735
|
entity |
| Predicate | hasGarrisonedFeature |
P27828
|
FINISHED |
| Object | Taiping Island |
—
|
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: Taiping Island | Statement: [Nansha Qundao, hasGarrisonedFeature, Taiping Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGarrisonedFeature Context triple: [Nansha Qundao, hasGarrisonedFeature, Taiping Island]
-
A.
hasGarrisonOutpostChoice
Indicates that an entity is associated with a selectable option regarding the placement or use of a garrison outpost.
-
B.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
C.
garrisonedUnit
chosen
Indicates that one unit is stationed inside, occupying, or defending another entity such as a building, vehicle, or fortification.
-
D.
hasFortressConstructed
Indicates that a fortress has been built or established for, by, or at the associated entity.
-
E.
hasFortifications
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:33 p.m.