Triple
T27290362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodlark Island |
E688604
|
entity |
| Predicate | hasMilitaryHistoryEvent |
P65457
|
FINISHED |
| Object | Operation Chronicle |
—
|
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: Operation Chronicle | Statement: [Woodlark Island, hasMilitaryHistoryEvent, Operation Chronicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryHistoryEvent Context triple: [Woodlark Island, hasMilitaryHistoryEvent, Operation Chronicle]
-
A.
hadMilitaryFollowing
Indicates that an entity was supported or backed by a group of military personnel or forces.
-
B.
associatedWithMilitaryHistory
chosen
Indicates a relationship in which something is connected or relevant to military history, such as events, figures, institutions, or artifacts.
-
C.
hadMilitaryPost
Indicates that an entity held an official position or assignment within a military organization.
-
D.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
E.
militaryEventMentionedIn
Indicates that a specific military event is referenced or discussed within a particular document, text, or source.
- 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 11:14 a.m.