Triple
T28772462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French state |
E726447
|
entity |
| Predicate | providesPublicFundingFor |
P33009
|
FINISHED |
| Object | regional rail transport in France |
—
|
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: regional rail transport in France | Statement: [French state, providesPublicFundingFor, regional rail transport in France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesPublicFundingFor Context triple: [French state, providesPublicFundingFor, regional rail transport in France]
-
A.
publiclyFunded
Indicates that the entity receives financial support from public sources such as government budgets or taxpayer funds.
-
B.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
C.
fundedEntityType
Indicates the type or category of entity that receives funding in the described funding relationship.
-
D.
federalFundingRequirement
Indicates that an entity is subject to a condition or standard that must be met in order to receive or maintain federal funding.
-
E.
funderOf
chosen
Indicates that one entity provides financial support or funding for another entity, project, 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 28, 2026, 6:16 a.m.