Triple
T33865145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Floating Piers |
E868026
|
entity |
| Predicate | postProjectAction |
P177489
|
FINISHED |
| Object | materials recycled |
—
|
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: materials recycled | Statement: [The Floating Piers, postProjectAction, materials recycled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postProjectAction Context triple: [The Floating Piers, postProjectAction, materials recycled]
-
A.
project
Indicates that an entity plans, organizes, or carries out a structured effort or initiative aimed at achieving a specific goal or outcome.
-
B.
exportProject
Indicates initiating the transfer or packaging of a project’s data or configuration from one system, format, or environment to another.
-
C.
projectPromoter
Indicates that an entity is responsible for initiating, supporting, or advocating for a particular project.
-
D.
shipProject
Indicates initiating, managing, or executing the delivery and release of a project from development to completion or deployment.
-
E.
projectModel
Indicates a relationship where one entity serves as a model, template, or representation for a project or projected outcome involving another entity.
- 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.