Triple
T23364935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl-Anthony |
E593288
|
entity |
| Predicate | nameBearerPosition |
P1082
|
FINISHED |
| Object | center |
—
|
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: center | Statement: [Karl-Anthony, nameBearerPosition, center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameBearerPosition Context triple: [Karl-Anthony, nameBearerPosition, center]
-
A.
nameBearerType
Indicates the specific role or capacity in which an entity bears or carries a given name (e.g., as a person, place, organization, or other type of name bearer).
-
B.
namePosition
chosen
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
C.
hasSurnameBearer
Indicates that a particular surname is borne or carried by a specific person or entity.
-
D.
nameBearerOfficeTermStart
Indicates the date or time when the office term associated with the name-bearing entity begins.
-
E.
bearerNameInPinyin
Indicates that the bearer’s name is represented in its pinyin (romanized Chinese) form.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ab7fc481908b496ec9b543eddd |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.