Triple
T5158745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wake Island |
E116380
|
entity |
| Predicate | annexedDate |
P9024
|
FINISHED |
| Object | 1899 |
—
|
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: 1899 | Statement: [Wake Island, annexedDate, 1899]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annexedDate Context triple: [Wake Island, annexedDate, 1899]
-
A.
annexationDate
chosen
Indicates the date on which one entity formally annexed or incorporated another entity into its territory or jurisdiction.
-
B.
annexedInYear
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
-
C.
annexedDuring
Indicates that one entity was formally incorporated into and brought under the control of another entity during a specified time period.
-
D.
wasAnnexedInPartition
Indicates that a territory or entity was incorporated into another as a result of a formal partition of land or political division.
-
E.
annexationInstrument
Indicates the legal or formal instrument (such as a treaty, decree, or law) by which one entity annexes or incorporates another.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.