Triple
T8501377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go Set a Watchman |
E201224
|
entity |
| Predicate | portraysAtticusAs |
P83074
|
FINISHED |
| Object | segregationist |
—
|
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: segregationist | Statement: [Go Set a Watchman, portraysAtticusAs, segregationist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysAtticusAs Context triple: [Go Set a Watchman, portraysAtticusAs, segregationist]
-
A.
portraysActorAs
Indicates that one entity depicts or represents an actor in a particular role, character, or manner.
-
B.
portraysAdamAs
Indicates that a subject represents or depicts Adam in a particular way, role, or characterization.
-
C.
wasPortrayedAs
Indicates that one entity has been depicted or represented in the form or role of another entity, typically within some medium or context.
-
D.
portrayedAsFrom
Indicates that one entity is depicted or represented as originating from, or belonging to, the place or source specified by another entity.
-
E.
portrayalFeature
Indicates that one entity serves as a characteristic, aspect, or attribute highlighted in the depiction or representation of another entity.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe59ad65c8190a2b8e6d22269853a |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:14 p.m.