Triple
T29786903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chou (Wade–Giles) |
E756288
|
entity |
| Predicate | systemRefinedBy |
P172401
|
FINISHED |
| Object | Herbert Giles |
—
|
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: Herbert Giles | Statement: [Chou (Wade–Giles), systemRefinedBy, Herbert Giles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemRefinedBy Context triple: [Chou (Wade–Giles), systemRefinedBy, Herbert Giles]
-
A.
systemUsedBy
Indicates that a particular system is utilized or operated by a specified agent or user.
-
B.
systemEntry
Indicates that an entity is being recorded, registered, or introduced into a particular system or structured environment.
-
C.
servedSystem
Indicates that one system has provided service, functionality, or resources to another system.
-
D.
systemSymbol
Indicates that one entity serves as the symbolic representation or notation used within a particular system for another entity or concept.
-
E.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
- 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_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 29, 2026, 5:09 p.m.