Triple
T33053113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World War II radio reports |
E845780
|
entity |
| Predicate | includedFormat |
P198651
|
FINISHED |
| Object | live reports |
—
|
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: live reports | Statement: [World War II radio reports, includedFormat, live reports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedFormat Context triple: [World War II radio reports, includedFormat, live reports]
-
A.
includeFormat
Indicates that one entity contains or specifies the format or representation type of another entity.
-
B.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
C.
containsFormat
chosen
Indicates that one entity includes or is associated with a particular format type as part of its content or representation.
-
D.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
E.
relatedFormat
Indicates that two resources are available in different but closely related formats or media representations of essentially the same content.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0238010fa481909b07a5c22aa0abde |
completed | May 11, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_6a0236cfdcb481908323b67b925c76d9 |
completed | May 11, 2026, 8:06 p.m. |
Created at: May 1, 2026, 1:24 a.m.