Triple
T14369915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maarten Baas |
E356331
|
entity |
| Predicate | knownForCombining |
P113766
|
FINISHED |
| Object | art |
—
|
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: art | Statement: [Maarten Baas, knownForCombining, art]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForCombining Context triple: [Maarten Baas, knownForCombining, art]
-
A.
symbolCombines
Indicates that multiple symbols are merged or joined together to form a single composite symbol or representation.
-
B.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
C.
combinesFeaturesOf
Indicates that one entity integrates or merges characteristics, attributes, or functionalities originating from multiple other entities.
-
D.
combiningClass
Indicates that one entity functions as a combining diacritic or mark that attaches to a base character, specifying how it combines in text rendering or encoding.
-
E.
originalCombinationFor
Indicates that one entity is the initial or source combination from which another combined entity is derived or constructed.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fb0b8988190ab834a85911c015c |
completed | April 14, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:15 a.m.