Triple
T1414764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pescadores Islands |
E31887
|
entity |
| Predicate | hasMilitarySignificance |
P27512
|
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: [Pescadores Islands, hasMilitarySignificance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitarySignificance Context triple: [Pescadores Islands, hasMilitarySignificance, true]
-
A.
hasMilitarySignificanceSince
Indicates that something has held military importance or strategic value starting from a specified point in time.
-
B.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
C.
militaryImportance
Indicates the degree to which something is strategically or operationally significant to military objectives or capabilities.
-
D.
hasNearbyMilitaryHistorySite
Indicates that an entity is located close to a site of historical military significance, such as a battlefield, fort, or memorial.
-
E.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3e5f9d08190861206934cd71fd8 |
completed | March 1, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c06721488190ac7f6e012f21af3d |
completed | March 1, 2026, 10:40 p.m. |
Created at: March 1, 2026, 7:59 p.m.