Triple
T28714368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weihsien |
E729916
|
entity |
| Predicate | notableInternee |
P203371
|
FINISHED |
| Object | Eric Liddell |
—
|
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: Eric Liddell | Statement: [Weihsien, notableInternee, Eric Liddell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInternee Context triple: [Weihsien, notableInternee, Eric Liddell]
-
A.
notableJunior
Indicates that one entity is a younger or less senior counterpart who is notably associated with another, more senior entity.
-
B.
notableInterviewee
Indicates that a person has been interviewed by another person or organization in a way considered significant or noteworthy.
-
C.
notableRecruit
Indicates that an entity is recognized as a significant or high-profile addition to an organization, group, or team.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableWorker
Indicates that the subject is a worker who is distinguished or recognized for being particularly important, prominent, or exemplary in their work.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a016ebba0448190b5319243e1b2feca |
completed | May 11, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a016d2486b4819085efe197ee21b707 |
completed | May 11, 2026, 5:46 a.m. |
| PDg | Predicate description generation | batch_6a016ebace208190af9a6d6d8a31c670 |
completed | May 11, 2026, 5:52 a.m. |
Created at: April 28, 2026, 5:50 a.m.