Triple
T12661733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Courante |
E302440
|
entity |
| Predicate | ItalianCorrenteCharacteristic |
P17157
|
FINISHED |
| Object | faster and more flowing |
—
|
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: faster and more flowing | Statement: [Courante, ItalianCorrenteCharacteristic, faster and more flowing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ItalianCorrenteCharacteristic Context triple: [Courante, ItalianCorrenteCharacteristic, faster and more flowing]
-
A.
ItalianObjective
Indicates that an entity has an objective, goal, or target specifically related to Italy or the Italian context.
-
B.
cuisineFeature
chosen
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
C.
isPastaFilata
Indicates that something is a pasta filata cheese, i.e., a cheese made by heating and stretching the curd in hot water.
-
D.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
E.
certificationItaly
Indicates that an entity holds or is associated with a certification that is specifically issued, recognized, or valid in Italy.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617c5b888190b37d4ede139bb49e |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:19 p.m.