Triple
T7406698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ferme générale |
E170888
|
entity |
| Predicate | keptAsProfit |
P29046
|
FINISHED |
| Object | surplus tax receipts over farmed amount |
—
|
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: surplus tax receipts over farmed amount | Statement: [Ferme générale, keptAsProfit, surplus tax receipts over farmed amount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keptAsProfit Context triple: [Ferme générale, keptAsProfit, surplus tax receipts over farmed amount]
-
A.
keptIn
Indicates that one entity is stored, contained, or maintained inside another entity as its location or container.
-
B.
profitsFrom
chosen
Indicates that one entity gains financial or material benefit as a result of another entity’s actions, existence, or situation.
-
C.
becameProfitable
Indicates that an entity transitioned from operating at a loss or break-even to generating a net profit.
-
D.
gainedBy
Indicates that something comes to possess, obtain, or receive something else as a result of an action, process, or event.
-
E.
earnOn
Indicates that one entity gains income, profit, or returns as a result of another entity or activity.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f275c6e481908b4ce9ff1e418296 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.