Triple
T31747719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taps |
E810316
|
entity |
| Predicate | firstUsedDuring |
P66076
|
FINISHED |
| Object | Peninsula Campaign |
E80108
|
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: Peninsula Campaign | Statement: [Taps, firstUsedDuring, Peninsula Campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedDuring Context triple: [Taps, firstUsedDuring, Peninsula Campaign]
-
A.
firstUsedAt
chosen
Indicates the time or place at which something was initially used or put into operation.
-
B.
firstUsedAs
Indicates that one entity was the earliest or original thing in which another entity was used or applied.
-
C.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
D.
firstProminentlyUsedAfter
Indicates that one entity began to be widely or notably used only after the time or event associated with another entity.
-
E.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b948524848190967dd21254f57026 |
completed | June 12, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:27 p.m.