Triple
T31326057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finanzamt |
E798888
|
entity |
| Predicate | collectsRevenueFor |
P100104
|
FINISHED |
| Object | federal government of Germany |
—
|
NE NERFINISHED |
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: federal government of Germany | Statement: [Finanzamt, collectsRevenueFor, federal government of Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsRevenueFor Context triple: [Finanzamt, collectsRevenueFor, federal government of Germany]
-
A.
revenue
Indicates the amount of income generated by an entity from its business activities or operations over a specified period.
-
B.
revenueSources
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
C.
revenuePaidTo
Indicates that a specified amount of revenue is paid or transferred from one entity to another as a recipient.
-
D.
revenueCollectionRelationship
chosen
Indicates a relationship where one entity is responsible for collecting or receiving revenue on behalf of or from another entity.
-
E.
hasRevenueUnit
Indicates that an entity’s revenue is measured, reported, or associated in terms of a specified unit (e.g., currency or measurement unit).
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 29, 2026, 9:15 p.m.