Triple
T17006691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hundred Family Surnames |
E412587
|
entity |
| Predicate | isMemorizedOrally |
P126175
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hundred Family Surnames, isMemorizedOrally, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMemorizedOrally Context triple: [Hundred Family Surnames, isMemorizedOrally, true]
-
A.
isMemorizedFor
Indicates that something has been committed to memory specifically for a particular purpose, context, or entity.
-
B.
memorizedBy
Indicates that some content, information, or material has been learned and retained in memory by a particular entity.
-
C.
memorizationPractice
Indicates engaging in activities or exercises specifically intended to commit information to memory or strengthen recall.
-
D.
isOftenRecitedFor
Indicates that something (such as a text, phrase, or piece of music) is frequently spoken, chanted, or performed for a particular purpose, audience, or occasion.
-
E.
notRecitedOn
Indicates that a particular text, prayer, or recitation was not performed or spoken on a specified occasion, time, or context.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d3831268819089286053a5acf653 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e378e037c88190935d732e0f10d5d7 |
completed | April 18, 2026, 12:28 p.m. |
Created at: April 10, 2026, 5:32 a.m.