Triple
T34163608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Augusta |
E876348
|
entity |
| Predicate | notableServicePeriod |
P146903
|
FINISHED |
| Object | before and during World War II |
—
|
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: before and during World War II | Statement: [USS Augusta, notableServicePeriod, before and during World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableServicePeriod Context triple: [USS Augusta, notableServicePeriod, before and during World War II]
-
A.
notableOfficePeriod
Indicates that an entity held a particular office or position during a specified time period.
-
B.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
C.
notablePeriodOfInterest
chosen
Indicates a time span that is particularly significant or noteworthy in relation to the subject.
-
D.
notableEventPeriod
Indicates the time span during which a notable or significant event associated with an entity took place.
-
E.
notablePeriodOfAward
Indicates the specific time span or period during which an award is considered notable or was actively held or recognized.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:54 a.m.