Triple
T35401713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choi |
E1023249
|
entity |
| Predicate | isCommonInFieldOfNotableBearers |
P116510
|
FINISHED |
| Object | literature |
—
|
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: literature | Statement: [Choi, isCommonInFieldOfNotableBearers, literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonInFieldOfNotableBearers Context triple: [Choi, isCommonInFieldOfNotableBearers, literature]
-
A.
hasNotableFieldOfBearers
Indicates that the entities share a significant or distinguished area of activity, expertise, or achievement associated with their bearers.
-
B.
hasNotableBearersType
Indicates that an entity has notable bearers belonging to a specified type or category.
-
C.
hasNotableBearerFamily
Indicates that a family is recognized for having at least one notable or distinguished member associated with it.
-
D.
typicalNameBearers
chosen
Indicates that the subject is a common or characteristic name borne by the entities in the object set.
-
E.
hasNotableSingleBearer
Indicates that the relationship holds when a name, title, or identifier is notably associated with exactly one specific bearer, rather than shared among many.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:03 p.m.