Triple
T31266558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Savage Place |
E797268
|
entity |
| Predicate | protagonistBaseOfOperations |
P177165
|
FINISHED |
| Object | Boston |
—
|
NE NERFINISHED |
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: Boston | Statement: [A Savage Place, protagonistBaseOfOperations, Boston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistBaseOfOperations Context triple: [A Savage Place, protagonistBaseOfOperations, Boston]
-
A.
protagonistLocation
chosen
Indicates the location or setting where the story’s main protagonist is situated at a given time.
-
B.
protagonistHomeworld
Indicates the homeworld or place of origin associated with a story’s main protagonist.
-
C.
antagonistLocationFor
Indicates that a location serves as the primary place where an antagonist operates, resides, or exerts influence in relation to a given context or entity.
-
D.
protagonistAllegiance
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
E.
placeOfMission
Indicates the location where a mission, assignment, or task is carried out or based.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 9:13 p.m.