Triple
T28772474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French state |
E726447
|
entity |
| Predicate | partiallyFunds |
P69143
|
FINISHED |
| Object | infrastructure used by TER Grand Est |
—
|
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: infrastructure used by TER Grand Est | Statement: [French state, partiallyFunds, infrastructure used by TER Grand Est]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyFunds Context triple: [French state, partiallyFunds, infrastructure used by TER Grand Est]
-
A.
partiallySupportedBy
chosen
Indicates that something receives incomplete, limited, or not fully sufficient support from another entity.
-
B.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
C.
partiallyFilledFor
Indicates that one entity is incompletely or partially filled in service of, or in relation to, another entity.
-
D.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
E.
includesFundingFor
Indicates that one entity’s financial resources or budget allocation explicitly cover or provide 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_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 6:16 a.m.