Triple
T24633297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017–18 Serie A Femminile |
E609735
|
entity |
| Predicate | hasFinalTable |
P80219
|
FINISHED |
| Object | 2017–18 Serie A Femminile league table |
—
|
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: 2017–18 Serie A Femminile league table | Statement: [2017–18 Serie A Femminile, hasFinalTable, 2017–18 Serie A Femminile league table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalTable Context triple: [2017–18 Serie A Femminile, hasFinalTable, 2017–18 Serie A Femminile league table]
-
A.
hasFinalStage
Indicates that an entity possesses or reaches a concluding or ultimate phase in a process, sequence, or lifecycle.
-
B.
hasFinalState
Indicates that an entity ultimately results in, transitions to, or ends in a specified final state or condition.
-
C.
hasFinalFormat
Indicates that an entity possesses or is associated with its completed, finalized version or representation.
-
D.
hasFinalFormUsage
Indicates that an entity is used or appears in its ultimate, completed, or final form within a given context or process.
-
E.
hasTables
chosen
Indicates that an entity possesses or contains one or more tables.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.