Triple
T27038026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chachaři |
E681108
|
entity |
| Predicate | supportsSince |
P198280
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Chachaři, supportsSince, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSince Context triple: [Chachaři, supportsSince, 20th century]
-
A.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
B.
supportedFrom
Indicates that one entity provides backing, assistance, or justification for another entity, often serving as the source or basis of that support.
-
C.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
D.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
-
E.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
| PDg | Predicate description generation | batch_69fed83a3b8c819092a3bd1ca9d9b38b |
completed | May 9, 2026, 6:46 a.m. |
Created at: April 27, 2026, 7:17 a.m.