Triple
T19961834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cemetery of Parma (project) |
E479832
|
entity |
| Predicate | unbuilt |
P18162
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cemetery of Parma (project), unbuilt, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unbuilt Context triple: [Cemetery of Parma (project), unbuilt, true]
-
A.
builtWithout
Indicates that something was constructed or created in the absence of a particular component, material, tool, or condition.
-
B.
unfinished
chosen
Indicates that an action, process, or state has started but has not yet been completed.
-
C.
notRebuiltAfter
Indicates that an entity was destroyed or damaged and has not been reconstructed or restored after a specified event or point in time.
-
D.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
E.
builtFrom
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af51b4c81909ba156a489cbc551 |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.