Triple
T8424057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenini |
E198932
|
entity |
| Predicate | hasRelatedFormType |
P21674
|
FINISHED |
| Object | plural form of Jenini |
—
|
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: plural form of Jenini | Statement: [Jenini, hasRelatedFormType, plural form of Jenini]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedFormType Context triple: [Jenini, hasRelatedFormType, plural form of Jenini]
-
A.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
B.
associatedWithForm
Indicates a relationship in which something is linked or connected to a particular form, document, or structured representation.
-
C.
relatedForm
chosen
Indicates that one entity is an alternative or variant form of another, such as a different spelling, inflection, or closely related lexical form.
-
D.
containsForm
Indicates that one entity includes or encapsulates another entity as a form, structure, or representation within it.
-
E.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
- 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.