Triple
T8408344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kutuzovsky Prospekt |
E198557
|
entity |
| Predicate | namedForOccupationOfHonouree |
P18120
|
FINISHED |
| Object | field marshal |
—
|
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: field marshal | Statement: [Kutuzovsky Prospekt, namedForOccupationOfHonouree, field marshal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForOccupationOfHonouree Context triple: [Kutuzovsky Prospekt, namedForOccupationOfHonouree, field marshal]
-
A.
namedForNationalityOfHonouree
Indicates that something is named in honor of a person, specifically referencing that person's nationality.
-
B.
honouredPersonOccupation
chosen
Indicates that the honored person is or was associated with a particular occupation or professional role.
-
C.
honoreeRole
Indicates the specific role, title, or capacity in which an individual is being honored in relation to an award, event, or recognition.
-
D.
namedPersonOccupation
Indicates that a person is explicitly identified as having a particular occupation or job role.
-
E.
honoredPerson
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
- 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb8315a8a8819097f6da11b909b527 |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.