Triple
T30473055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cloud (Museum de Fundatie) |
E775358
|
entity |
| Predicate | hasSurfaceTexture |
P196285
|
FINISHED |
| Object | tiled |
—
|
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: tiled | Statement: [The Cloud (Museum de Fundatie), hasSurfaceTexture, tiled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceTexture Context triple: [The Cloud (Museum de Fundatie), hasSurfaceTexture, tiled]
-
A.
hasSurfaceOperations
Indicates that an entity performs, supports, or is associated with activities or operations occurring on a surface.
-
B.
hasImageSurface
Indicates that one entity possesses or is associated with a surface suitable for displaying or bearing an image.
-
C.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
D.
hasSurfacePreference
Indicates that an entity tends to favor or is best suited for interacting with a particular type of surface over others.
-
E.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69fe1fd58ad8819093d3d705e8521014 |
completed | May 8, 2026, 5:39 p.m. |
Created at: April 29, 2026, 8:11 p.m.