Triple
T11270484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasure Island, San Francisco, California, United States |
E266797
|
entity |
| Predicate | militaryUseStartYear |
P15394
|
FINISHED |
| Object | 1941 |
—
|
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: 1941 | Statement: [Treasure Island, San Francisco, California, United States, militaryUseStartYear, 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryUseStartYear Context triple: [Treasure Island, San Francisco, California, United States, militaryUseStartYear, 1941]
-
A.
firstCombatUseDate
Indicates the date on which something (typically a weapon, system, or tactic) was first used in actual combat.
-
B.
militaryUseEnd
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
-
C.
hasMilitarySignificanceSince
chosen
Indicates that something has held military importance or strategic value starting from a specified point in time.
-
D.
historicalPeriodOfFirstUse
Indicates the historical time period during which something was first used or came into use.
-
E.
firstMajorUseYear
Indicates the calendar year in which something was first put into major or primary use.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9506204819089dc0827483bd948 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d7879bc56c8190b2e8d2193f29de05 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.