Triple
T28359180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danubian front of the Crimean War |
E718315
|
entity |
| Predicate | involvedOccupationOf |
P180504
|
FINISHED |
| Object | Moldavia |
—
|
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: Moldavia | Statement: [Danubian front of the Crimean War, involvedOccupationOf, Moldavia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedOccupationOf Context triple: [Danubian front of the Crimean War, involvedOccupationOf, Moldavia]
-
A.
requiredOccupationOf
Indicates that one entity specifies the occupation or job role that is required or expected for another entity (such as a position, task, or qualification).
-
B.
involvedInWork
Indicates that an entity participates in, contributes to, or is otherwise engaged in a particular work, project, or activity.
-
C.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
D.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
E.
eraOfOccupation
Indicates the time period during which an occupation or role was held or practiced.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 28, 2026, 12:51 a.m.