Triple
T34947671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larzac military camp |
E1007897
|
entity |
| Predicate | expansionPlanOpposedBy |
P119957
|
FINISHED |
| Object | local farmers |
—
|
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: local farmers | Statement: [Larzac military camp, expansionPlanOpposedBy, local farmers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionPlanOpposedBy Context triple: [Larzac military camp, expansionPlanOpposedBy, local farmers]
-
A.
proposedDevelopmentOpposed
chosen
Indicates that one party expresses opposition or resistance to a suggested or planned development.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
opposedProject
Indicates that an entity actively resisted, disagreed with, or worked against a particular project.
-
D.
opposedDuring
Indicates that one entity actively resisted or was in conflict with another entity during a specified time period or event.
-
E.
opposedByLeader
Indicates that an action, proposal, or position is actively resisted or rejected by a leader.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4 p.m.