Triple
T22644034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudepoêma |
E558907
|
entity |
| Predicate | hasTextureFeature |
P96596
|
FINISHED |
| Object | thick chordal writing |
—
|
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: thick chordal writing | Statement: [Rudepoêma, hasTextureFeature, thick chordal writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTextureFeature Context triple: [Rudepoêma, hasTextureFeature, thick chordal writing]
-
A.
usesTexture
Indicates that one entity employs or incorporates the texture of another entity in its appearance, design, or representation.
-
B.
textureFeatures
chosen
Indicates that one entity possesses or is characterized by specific surface or material texture properties described by the other entity.
-
C.
hasImageFeature
Indicates that an entity is associated with a specific visual characteristic or attribute extracted from an image.
-
D.
hasSurfaceFeatureState
Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
-
E.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
- F. None of above.
Provenance (3 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f170366ac881909e9d1dd2e7cf7a25 |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.