Triple
T33075249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laetitiae |
E846341
|
entity |
| Predicate | grammaticalCaseFormOf |
P140011
|
FINISHED |
| Object | Laetitia |
—
|
NE NERFINISHED |
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: Laetitia | Statement: [Laetitiae, grammaticalCaseFormOf, Laetitia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grammaticalCaseFormOf Context triple: [Laetitiae, grammaticalCaseFormOf, Laetitia]
-
A.
grammaticalForm
Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
-
B.
grammaticalCaseSystem
Indicates a relationship where a language employs a system of grammatical cases to mark the roles and relationships of nouns and related elements in sentences.
-
C.
hasCaseForms
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
-
D.
grammaticalCaseOf_Dei
chosen
Indicates that one entity specifies the grammatical case associated with the word or expression represented by the other entity.
-
E.
numberOfGrammaticalCases
Indicates the relationship that specifies how many distinct grammatical cases a language or linguistic system possesses.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:25 a.m.