Triple
T16584732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shipwreck (Broadway, 2006–2007) |
E402923
|
entity |
| Predicate | hasBroadConcept |
P531
|
FINISHED |
| Object | Russian history in literature |
—
|
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: Russian history in literature | Statement: [Shipwreck (Broadway, 2006–2007), hasBroadConcept, Russian history in literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadConcept Context triple: [Shipwreck (Broadway, 2006–2007), hasBroadConcept, Russian history in literature]
-
A.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
B.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
C.
isBroad
Indicates that something has a large width or extensive scope relative to a reference or context.
-
D.
isBroadBased
Indicates that something has a wide scope or foundation, encompassing many elements, aspects, or participants rather than being narrow or limited.
-
E.
hasConceptualParallel
Indicates that one entity corresponds to or mirrors another at a conceptual level, showing a similar idea, structure, or pattern despite possible differences in form or context.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3599b057881909fcb8bbb156633a8 |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.