Triple
T17111563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zengzi |
E415237
|
entity |
| Predicate | inConfucianLineage |
P39819
|
FINISHED |
| Object | second generation disciple |
—
|
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: second generation disciple | Statement: [Zengzi, inConfucianLineage, second generation disciple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inConfucianLineage Context triple: [Zengzi, inConfucianLineage, second generation disciple]
-
A.
patriarchalLineage
Indicates a familial relationship where descent, inheritance, or identity is traced through the male line or father’s ancestry.
-
B.
ancestralWorship
Indicates a relationship where one party performs rituals, offerings, or reverence directed toward their ancestors.
-
C.
veneratedInDynasty
Indicates that an entity was revered, honored, or held in high esteem during a specific historical dynasty.
-
D.
heritageLine
chosen
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
-
E.
divineLineage
Indicates that one entity is descended from, or originates from, a divine or god-like being.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2bab0881908339ec7fb3ebe7e9 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.