Triple
T23326352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love |
E591302
|
entity |
| Predicate | isCentralThemeIn |
P6627
|
FINISHED |
| Object | 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: literature | Statement: [Love, isCentralThemeIn, literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralThemeIn Context triple: [Love, isCentralThemeIn, literature]
-
A.
hasCentralTheme
chosen
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
-
B.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
C.
containsThemeArea
Indicates that one entity includes or encompasses a specific thematic area as part of its scope or content.
-
D.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
-
E.
centralThemeContext
Indicates that one concept serves as the main thematic focus within the situational, narrative, or discourse context defined by another.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197eaa7b88190aad2096c110dadea |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:12 p.m.