Triple
T29786877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chou |
E756287
|
entity |
| Predicate | moreTraditionalThan |
P167876
|
FINISHED |
| Object | Zhou |
—
|
NE NERFINISHED |
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: Zhou | Statement: [Chou, moreTraditionalThan, Zhou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moreTraditionalThan Context triple: [Chou, moreTraditionalThan, Zhou]
-
A.
modernTradition
Indicates a relationship where a practice or custom is recognized as a contemporary development that functions like a tradition within a culture or group.
-
B.
traditionalHeir
Indicates that one entity is recognized as the customary or culturally designated inheritor or successor of another entity.
-
C.
establishedTradition
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
D.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
-
E.
traditionalAncestor
Indicates that one entity is regarded as an ancestor of another according to traditional, customary, or culturally transmitted lineage beliefs rather than strictly documented genealogical records.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674abd4bc81908993a7677238b80c |
completed | May 2, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 29, 2026, 5:09 p.m.