Triple
T25724971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton Plan |
E645093
|
entity |
| Predicate | influencedBySystem |
P25489
|
FINISHED |
| Object | British constitutional system |
—
|
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: British constitutional system | Statement: [Hamilton Plan, influencedBySystem, British constitutional system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influencedBySystem Context triple: [Hamilton Plan, influencedBySystem, British constitutional system]
-
A.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
B.
effectOnSystem
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
-
C.
influencedByCurrent
Indicates that something’s state, behavior, or outcome is affected or determined by the current conditions, context, or situation.
-
D.
operatedOnSystem
Indicates that an entity has performed operations or actions upon a particular system, affecting its state or behavior.
-
E.
areAffectedBy
chosen
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 21, 2026, 10:17 p.m.