Triple
T1319713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juventus FC |
E28187
|
entity |
| Predicate | regularIn |
P12230
|
FINISHED |
| Object | European club competitions |
—
|
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: European club competitions | Statement: [Juventus FC, regularIn, European club competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularIn Context triple: [Juventus FC, regularIn, European club competitions]
-
A.
typicalIn
chosen
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
B.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
C.
regularization
Indicates the application of a constraint or penalty to a model or function to prevent overfitting and encourage simpler, more generalizable behavior.
-
D.
standardMaintained
Indicates that a specified standard is being upheld, preserved, or kept in compliance over time within the relevant context.
-
E.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c179883c8190b68fbeebb9696982 |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.