Triple
T10108614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Tax in Kind |
E218184
|
entity |
| Predicate | replacesPolicy |
P29646
|
FINISHED |
| Object | grain requisitioning |
—
|
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: grain requisitioning | Statement: [On the Tax in Kind, replacesPolicy, grain requisitioning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesPolicy Context triple: [On the Tax in Kind, replacesPolicy, grain requisitioning]
-
A.
replacedPolicyApproach
Indicates that one policy approach has been superseded and taken the place of another policy approach.
-
B.
changePolicy
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
-
C.
seeksToReplace
Indicates an intention or effort by one entity to take over the role, function, or position currently held by another entity.
-
D.
replacesInPractice
Indicates that one entity has effectively taken over the role, function, or use of another entity in real-world application or usage.
-
E.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0cbd8a48190b2af6177d1249f58 |
completed | April 2, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:03 p.m.