Triple
T29786879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chou |
E756287
|
entity |
| Predicate | stillFoundIn |
P162209
|
FINISHED |
| Object | personal names |
—
|
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: personal names | Statement: [Chou, stillFoundIn, personal names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillFoundIn Context triple: [Chou, stillFoundIn, personal names]
-
A.
isAlsoFoundIn
chosen
Indicates that the same entity or item occurs or exists in another specified location, context, or collection as well.
-
B.
ashFoundIn
Indicates that ash is present within, or has been discovered in, a specified location or material.
-
C.
foundAs
Indicates that one entity is discovered, identified, or observed in the role, form, or state represented by another entity.
-
D.
foundInRite
Indicates that something (such as an element, object, or action) occurs within, is used in, or is otherwise present as part of a specific rite or ritual.
-
E.
foundWith
Indicates that one entity is discovered, observed, or obtained in the presence or company of another entity.
- 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_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. |
Created at: April 29, 2026, 5:09 p.m.