Triple
T32385520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lishu |
E827534
|
entity |
| Predicate | strokeFeatures |
P147751
|
FINISHED |
| Object | thick horizontal strokes |
—
|
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 horizontal strokes | Statement: [Lishu, strokeFeatures, thick horizontal strokes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strokeFeatures Context triple: [Lishu, strokeFeatures, thick horizontal strokes]
-
A.
spanFeature
Indicates a relationship where a feature or characteristic extends across or covers a specified span or interval.
-
B.
markingFeature
Indicates a feature that serves as a distinguishing mark or identifier associated with an entity.
-
C.
strokeEvents
Indicates that one entity experiences, causes, or is associated with stroke-related medical events in relation to another entity or context.
-
D.
inkFeatures
chosen
Indicates that an entity possesses specific ink-related characteristics or properties.
-
E.
inscriptionFeature
Indicates that one entity bears or contains an inscribed element or marking that is treated as a notable feature in relation to another entity.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1cf2aa081909f4c0b8f0cad1907 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:51 a.m.