Triple
T36481206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joan Watson |
E898819
|
entity |
| Predicate | notableChangeFromSource |
P13888
|
FINISHED |
| Object | American rather than British |
—
|
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: American rather than British | Statement: [Joan Watson, notableChangeFromSource, American rather than British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableChangeFromSource Context triple: [Joan Watson, notableChangeFromSource, American rather than British]
-
A.
notableChange
chosen
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
-
B.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
C.
namespaceChangedFrom
Indicates that an entity’s namespace has been modified, specifying the previous namespace it was changed from.
-
D.
notableRuleChange
Indicates a significant modification to an established rule or set of rules that meaningfully alters how they apply or are enforced.
-
E.
namespaceChangedTo
Indicates that an entity’s namespace has been updated or reassigned from its previous value to a new one.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.