Triple
T18544297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | aedile |
E453181
|
entity |
| Predicate | oftenFinanced |
P65734
|
FINISHED |
| Object | public games from personal funds |
—
|
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: public games from personal funds | Statement: [aedile, oftenFinanced, public games from personal funds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenFinanced Context triple: [aedile, oftenFinanced, public games from personal funds]
-
A.
coFinancingRequirement
Indicates that an action, project, or agreement requires additional financial contribution from one or more other parties beyond the primary source of funding.
-
B.
loanSource
Indicates that one entity is the origin or provider of a loan extended to another entity.
-
C.
oftenProvides
chosen
Indicates that one entity frequently or regularly supplies, offers, or makes another entity available.
-
D.
agreedFastStartFinance
Indicates that an entity has formally agreed to participate in or support the Fast Start Finance initiative or arrangement.
-
E.
oftenConfiguredAs
Indicates that one entity is frequently set up, arranged, or used in the form or role of another entity.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b935c48190a34b17eeae4fd583 |
completed | April 19, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.