Triple
T9801369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basin City |
E237843
|
entity |
| Predicate | dominantThemes |
P7671
|
FINISHED |
| Object | vigilantism |
—
|
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: vigilantism | Statement: [Basin City, dominantThemes, vigilantism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantThemes Context triple: [Basin City, dominantThemes, vigilantism]
-
A.
majorThemeAssociation
Indicates that one entity is associated with another as a primary or central theme.
-
B.
notableTheme
chosen
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
-
C.
thematicConcept
Indicates that one entity embodies, expresses, or is centrally concerned with a particular underlying theme or conceptual idea represented by the other entity.
-
D.
culturalThemes
Indicates that there is a relationship between entities where one embodies, expresses, or is associated with particular cultural themes present in or derived from the other.
-
E.
themeHighlights
Indicates that certain elements are emphasized or visually distinguished as key features within a particular theme.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda62a11a88190880e0cce24923b14 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.