Triple
T37755554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fabricius |
E941100
|
entity |
| Predicate | namingConventionPart |
P189001
|
FINISHED |
| Object | tria nomina |
—
|
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: tria nomina | Statement: [Fabricius, namingConventionPart, tria nomina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingConventionPart Context triple: [Fabricius, namingConventionPart, tria nomina]
-
A.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
B.
namespaceConvention
Indicates the naming and structural rules that govern how namespaces are defined, organized, and referenced in a system.
-
C.
namingConventionContext
Indicates the contextual rules or patterns that govern how something is named within a particular system or setting.
-
D.
namingConventionRegion
Indicates that there is a specific regional or locale-based rule or pattern governing how something is named.
-
E.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
- F. None of above. chosen
Provenance (4 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaf48ba148190a8bdfd6846ad0540 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaeef9c488190babb546b962b4fb6 |
completed | May 6, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.