Triple
T30677149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 隨 |
E780944
|
entity |
| Predicate | totalStrokes |
P58361
|
FINISHED |
| Object | 12–13 (depending on writing standard) |
—
|
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: 12–13 (depending on writing standard) | Statement: [隨, totalStrokes, 12–13 (depending on writing standard)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalStrokes Context triple: [隨, totalStrokes, 12–13 (depending on writing standard)]
-
A.
hasStrokeCount
chosen
Indicates the number of strokes required to write a given symbol or character.
-
B.
hasStrokeCountApprox
Indicates an approximate number of strokes associated with writing or drawing the related entity.
-
C.
numberOfStrokesPerCycle
Indicates the count of individual strokes that occur during one complete cycle of a repeated action or process.
-
D.
radicalStrokeCount
Indicates the number of strokes used to write the radical component of a character.
-
E.
hasStrokeOrder
Indicates that there is a specific, ordered sequence of strokes used to write or draw the related symbol or character.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 8:32 p.m.