Triple
T32811947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolya |
E839176
|
entity |
| Predicate | canBeFormalizedAs |
P196878
|
FINISHED |
| Object | Nikolay |
—
|
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: Nikolay | Statement: [Kolya, canBeFormalizedAs, Nikolay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeFormalizedAs Context triple: [Kolya, canBeFormalizedAs, Nikolay]
-
A.
isFormalizedBy
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
-
B.
formalizedUnder
Indicates that something has been officially established, defined, or codified within the framework, authority, or provisions of a particular formal system, agreement, or institution.
-
C.
hasCanonicalFormulation
Indicates that one entity is the standard or officially accepted formulation or expression of another entity.
-
D.
formalization
Indicates that an informal concept, process, or agreement is being expressed, structured, or codified in a formal, explicit, and often standardized way.
-
E.
formalizedAt
Indicates the point in time or event at which something is officially established, documented, or given formal status.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fe6c7fc4388190aa88993d00872d7f |
completed | May 8, 2026, 11:06 p.m. |
Created at: May 1, 2026, 1:15 a.m.