Triple
T34980681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | True Detective |
E1008803
|
entity |
| Predicate | usesHistoricalFigures |
P53504
|
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: [True Detective, usesHistoricalFigures, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHistoricalFigures Context triple: [True Detective, usesHistoricalFigures, true]
-
A.
usesRealHistoricalFigures
chosen
Indicates that the work includes or depicts actual people from real history rather than entirely fictional characters.
-
B.
basedOnHistoricalFigure
Indicates that something is derived from, inspired by, or modeled after a real historical person.
-
C.
numberOfHistoricalFiguresAssociated
Indicates the count of historical figures that are linked or connected to a given entity.
-
D.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
E.
addressesHistoricalFigure
Indicates that one entity directly speaks or writes to a person recognized as a historical figure.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.