Triple
T20566316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yan Hui |
E504973
|
entity |
| Predicate | relationshipToConfucius |
P140585
|
FINISHED |
| Object | favorite 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: favorite disciple | Statement: [Yan Hui, relationshipToConfucius, favorite disciple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToConfucius Context triple: [Yan Hui, relationshipToConfucius, favorite disciple]
-
A.
relationshipToSocrates
Indicates the specific familial, social, or conceptual connection that one entity has to Socrates.
-
B.
philosophicalRelationTo
Indicates a conceptual or theoretical connection one entity holds toward another within a philosophical framework or viewpoint.
-
C.
relationshipToArichAnpin
Indicates a relational connection or association that an entity has to Arich Anpin within a given spiritual, hierarchical, or conceptual framework.
-
D.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
E.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a228948190b47a3a61f239e00d |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:39 a.m.