Triple
T36783874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kennedy Island |
E908845
|
entity |
| Predicate | hasNotableMilitaryUnitAssociated |
P22805
|
FINISHED |
| Object | PT-109 |
E870990
|
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: PT-109 | Statement: [Kennedy Island, hasNotableMilitaryUnitAssociated, PT-109]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMilitaryUnitAssociated Context triple: [Kennedy Island, hasNotableMilitaryUnitAssociated, PT-109]
-
A.
hasNotableMilitaryFigure
Indicates that an entity is associated with or distinguished by a specific person recognized for significant military role, rank, or achievements.
-
B.
hasNoStandingArmy
Indicates that a country or political entity does not maintain a permanent, professional military force.
-
C.
hasNotableNation
Indicates that an entity is significantly associated with or recognized for a particular nation.
-
D.
hasNotableWar
Indicates that an entity is associated with a significant or historically important war.
-
E.
hasMilitaryAssociation
chosen
Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d17a14084819097f1a7b036a3c9fd |
completed | June 25, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.