Triple
T25876199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big Broadcast of 1937 |
E651907
|
entity |
| Predicate | hasRevueStructure |
P191957
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Big Broadcast of 1937, hasRevueStructure, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevueStructure Context triple: [The Big Broadcast of 1937, hasRevueStructure, true]
-
A.
hasArticleStructure
Indicates that one entity possesses or follows a specific article-like structural organization (e.g., sections, headings, or layout).
-
B.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
C.
hasStructureHistory
Indicates that there exists a record or account detailing the past states, changes, or development of a structure over time.
-
D.
hasMainStructure
Indicates that one entity serves as the primary or central structural component of another entity.
-
E.
hasStructureLevel
Indicates a relationship where one entity possesses, is assigned, or is characterized by a particular structural level within a hierarchy or layered organization.
- F. None of above. chosen
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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: April 22, 2026, 8:12 a.m.