Triple
T28854765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orvietani |
E728703
|
entity |
| Predicate | useGentilicInItalianPluralFeminine |
P105483
|
FINISHED |
| Object | "orvietane" |
—
|
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: "orvietane" | Statement: [Orvietani, useGentilicInItalianPluralFeminine, "orvietane"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useGentilicInItalianPluralFeminine Context triple: [Orvietani, useGentilicInItalianPluralFeminine, "orvietane"]
-
A.
usesGentilicFor
chosen
Indicates that one entity refers to another using a gentilic (a demonym or term denoting origin, nationality, or regional affiliation).
-
B.
hasGenderInItalian
Indicates that an entity is associated with a specific grammatical gender when expressed in the Italian language.
-
C.
gentilicium
Indicates that an entity’s family or clan affiliation is expressed through a gentilic (family) name.
-
D.
genderedPluralForm
Indicates that the plural form of a term is specifically marked or inflected to reflect a particular gender.
-
E.
latinGenitive
Indicates that one entity is in the Latin genitive case in relation to another, typically expressing possession, origin, or association.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 6:45 a.m.