Triple
T17868346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meșterul Manole |
E446763
|
entity |
| Predicate | taskInLegend |
P93485
|
FINISHED |
| Object | building Curtea de Argeș Monastery |
—
|
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: building Curtea de Argeș Monastery | Statement: [Meșterul Manole, taskInLegend, building Curtea de Argeș Monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskInLegend Context triple: [Meșterul Manole, taskInLegend, building Curtea de Argeș Monastery]
-
A.
taskInPlot
chosen
Indicates that a specific task occurs within, is associated with, or is part of a particular plot or storyline.
-
B.
taskName
Indicates the specific name or label assigned to a task within a process or workflow.
-
C.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
D.
taskDomain
Indicates that a task belongs to, is categorized under, or is associated with a particular domain or area of activity.
-
E.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49aa0b69081909fba3b42d237b543 |
completed | April 19, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.