Triple
T24662045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chondoism |
E610563
|
entity |
| Predicate | founderHonorificName |
P96161
|
FINISHED |
| Object | Su-un |
—
|
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: Su-un | Statement: [Chondoism, founderHonorificName, Su-un]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderHonorificName Context triple: [Chondoism, founderHonorificName, Su-un]
-
A.
founderHonorific
chosen
Indicates that an honorific title or respectful designation is used when referring to the founder in this relationship.
-
B.
founderHonorificTitle
Indicates that an entity holds an honorific or ceremonial title specifically in their capacity as a founder.
-
C.
founderTitle
Indicates the formal role or title held by a person in their capacity as a founder of an organization or entity.
-
D.
founderAlsoKnownAs
Indicates that an individual who is a founder of something is also known by an alternative name or alias.
-
E.
founderKnownFor
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 2:34 a.m.