Triple
T17737947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villeurbannais |
E442772
|
entity |
| Predicate | hasPluralSense |
P912
|
FINISHED |
| Object | group of inhabitants of Villeurbanne |
—
|
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: group of inhabitants of Villeurbanne | Statement: [Villeurbannais, hasPluralSense, group of inhabitants of Villeurbanne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPluralSense Context triple: [Villeurbannais, hasPluralSense, group of inhabitants of Villeurbanne]
-
A.
hasPluralForm
Indicates that one term is the plural grammatical form of another term.
-
B.
hasPlurality
chosen
Indicates that an entity or concept exists or is expressed in a plural form rather than a singular one.
-
C.
hasMultipleMeanings
Indicates that a term, symbol, or expression is associated with more than one distinct meaning or interpretation.
-
D.
hasSense
Indicates that an entity possesses or is associated with a particular sensory perception, meaning, or interpretation.
-
E.
hasGrammaticalNumber
Indicates that an expression is associated with a specific grammatical number category (such as singular, plural, or dual) in a 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47aca27448190943c75e723ceefcc |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:09 a.m.