Triple
T18978935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthonij |
E464369
|
entity |
| Predicate | isModernStandardForm |
P13699
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Anthonij, isModernStandardForm, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isModernStandardForm Context triple: [Anthonij, isModernStandardForm, no]
-
A.
standardModernForm
chosen
Indicates that an entity is expressed or represented in the currently accepted standard modern form of a language, notation, or system.
-
B.
hasModernFormulationIn
Indicates that something has a contemporary or updated version expressed or formulated within a specified context, framework, or medium.
-
C.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
D.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
E.
isModernLine
Indicates that something belongs to, represents, or conforms to a contemporary or current-era style, design, or version within a series or category.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d621e3e08190b2d1d969ecaa380b |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.