Triple
T31207885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophronia |
E795650
|
entity |
| Predicate | isLinguisticCategory |
P7162
|
FINISHED |
| Object | proper noun |
—
|
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: proper noun | Statement: [Sophronia, isLinguisticCategory, proper noun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLinguisticCategory Context triple: [Sophronia, isLinguisticCategory, proper noun]
-
A.
linguisticType
Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
-
B.
linguisticClassification
Indicates the relationship by which an entity is categorized according to its language or linguistic type.
-
C.
hasLinguisticDomain
Indicates that something (such as a term, expression, or resource) is associated with or applies within a particular linguistic domain or language context.
-
D.
hasLinguisticFeature
chosen
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
-
E.
hasLinguisticDataType
Indicates that something is associated with or characterized by a specific type or category of linguistic data.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c24de048190973b05290ff5c404 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:09 p.m.