Triple
T25876587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modicani |
E651917
|
entity |
| Predicate | usesGentilicFeminine |
P52140
|
FINISHED |
| Object | Modicana |
—
|
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: Modicana | Statement: [Modicani, usesGentilicFeminine, Modicana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGentilicFeminine Context triple: [Modicani, usesGentilicFeminine, Modicana]
-
A.
usesGentilicFor
Indicates that one entity refers to another using a gentilic (a demonym or term denoting origin, nationality, or regional affiliation).
-
B.
gentilicium
Indicates that an entity’s family or clan affiliation is expressed through a gentilic (family) name.
-
C.
honorificGender
Indicates that a particular honorific or title is associated with a specific gender or gendered form.
-
D.
hasGrammaticalGender
Indicates that one entity assigns or possesses a specific grammatical gender in relation to another entity (such as a word, phrase, or linguistic unit).
-
E.
hasFeminineFormInSomeLanguages
chosen
Indicates that the referenced entity has a distinct feminine grammatical or lexical form in at least one language.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f602e179ec8190aa45a4614673f7fc |
completed | May 2, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:13 a.m.