Triple
T8424055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenini |
E198932
|
entity |
| Predicate | hasNumberForm |
P35097
|
FINISHED |
| Object | singular |
—
|
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: singular | Statement: [Jenini, hasNumberForm, singular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberForm Context triple: [Jenini, hasNumberForm, singular]
-
A.
hasOppositeNumberForm
Indicates that one entity is represented by a number form that is the opposite (e.g., additive vs. subtractive, positive vs. negative, or otherwise contrastive) of the number form used to represent the other entity.
-
B.
hasNumeral
Indicates that one entity is associated with a numeral representation or numeric symbol of another entity.
-
C.
hasNumberDistinction
chosen
Indicates that a language or system grammatically distinguishes between different numbers (such as singular, plural, dual, etc.) in its expressions.
-
D.
hasNumberCategory
Indicates that an entity is associated with a specific numerical classification or type.
-
E.
hasNumberSystem
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb85a0d04481908a5da908cafeceaa |
completed | March 31, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:07 p.m.