Triple
T12540771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Adult Science Fiction and Fantasy |
E299830
|
entity |
| Predicate | hasCommonPlotElement |
P105790
|
FINISHED |
| Object | chosen one trope |
—
|
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: chosen one trope | Statement: [Young Adult Science Fiction and Fantasy, hasCommonPlotElement, chosen one trope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonPlotElement Context triple: [Young Adult Science Fiction and Fantasy, hasCommonPlotElement, chosen one trope]
-
A.
hasCommonValue
Indicates that two or more entities share at least one identical value or attribute in common.
-
B.
hasCommonReference
Indicates that two or more entities share the same source, citation, or referential basis.
-
C.
hasSubplot
Indicates that a narrative work contains a secondary, subordinate storyline in addition to its main plot.
-
D.
hasCommonSpace
Indicates that two or more entities share access to the same physical or virtual area intended for joint or overlapping use.
-
E.
hasCommonShape
Indicates that two or more entities share the same or a very similar geometric or visual shape.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95f5148948190946a575d812b329d |
completed | April 10, 2026, 8:36 p.m. |
Created at: April 8, 2026, 9:57 p.m.