Triple
T36455856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zongtang |
E898148
|
entity |
| Predicate | familyNameWithWhichItIsBestKnown |
P149002
|
FINISHED |
| Object | Zuo |
—
|
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: Zuo | Statement: [Zongtang, familyNameWithWhichItIsBestKnown, Zuo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNameWithWhichItIsBestKnown Context triple: [Zongtang, familyNameWithWhichItIsBestKnown, Zuo]
-
A.
isWidelyKnownAs
Indicates that an entity is commonly referred to or recognized by a particular name or label by a broad audience.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
isBestKnownFrom
Indicates that an entity is primarily or most famously recognized in connection with a particular source, context, or work.
-
D.
notableFamilyNameOf
chosen
Indicates that a particular family name is notably or prominently associated with a given person or family entity.
-
E.
knownInHistoryAs
Indicates that an entity is recognized or referred to by a particular name or title in historical records or accounts.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:10 p.m.