Triple
T1042686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nullius in verba |
E22502
|
entity |
| Predicate | verbaCase |
P12254
|
FINISHED |
| Object | accusative plural |
—
|
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: accusative plural | Statement: [Nullius in verba, verbaCase, accusative plural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verbaCase Context triple: [Nullius in verba, verbaCase, accusative plural]
-
A.
verseForm
Indicates the specific structural or metrical pattern in which a verse or poem is composed.
-
B.
numberOfGrammaticalCases
Indicates the relationship that specifies how many distinct grammatical cases a language or linguistic system possesses.
-
C.
hasCaseForms
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
-
D.
grammaticalForm
Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
-
E.
hasCaseMarking
chosen
Indicates that a linguistic element (such as a noun or pronoun) bears a specific grammatical case marking that signals its syntactic or semantic role in a clause.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b845fa8c8190a7b69629883b62e2 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.