Triple
T6042550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nemo |
E134580
|
entity |
| Predicate | caseSystem |
P23828
|
FINISHED |
| Object | Latin declension |
—
|
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: Latin declension | Statement: [Nemo, caseSystem, Latin declension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseSystem Context triple: [Nemo, caseSystem, Latin declension]
-
A.
usesCaseSystem
chosen
Indicates that one entity employs or operates using a particular case system (e.g., grammatical or structural case-marking system).
-
B.
usesCaseManagementSystem
Indicates that an entity makes use of a case management system to organize, track, or handle cases or workflows.
-
C.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
D.
classificationSystem
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
E.
classificationSystemName
Indicates the name or label assigned to a particular classification system used to categorize or organize 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_69c00876a69881908088a2626d3b2666 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056e108fc81908775d176ff960fad |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049eb52a08190ac10fd703735f5aa |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.