Triple
T33865148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Floating Piers |
E868026
|
entity |
| Predicate | posthumousRealization |
P177490
|
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: [The Floating Piers, posthumousRealization, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousRealization Context triple: [The Floating Piers, posthumousRealization, true]
-
A.
posthumousAction
Indicates an action or event that occurs or is carried out after the death of the person to whom it relates.
-
B.
posthumousPresence
Indicates the continued influence, impact, or perceived presence of an entity after its death or cessation of existence.
-
C.
posthumousForm
Indicates a form, version, or representation of something that is created, recognized, or exists only after the death of the associated entity.
-
D.
posthumousSuccess
Indicates that an entity achieves recognition, fame, or significant success only after its creator or originator has died.
-
E.
posthumousAssociation
Indicates an association or connection between entities that is established, recognized, or relevant only after one of the entities has died.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700a15edc8190a338cb7d5b703b9d |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6fcc44af48190b95fb9e12480a85f |
completed | May 3, 2026, 7:44 a.m. |
Created at: May 1, 2026, 1:47 a.m.