Triple
T28490221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ong |
E720943
|
entity |
| Predicate | meaningOfSourceSurname |
P86557
|
FINISHED |
| Object | king |
—
|
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: king | Statement: [Ong, meaningOfSourceSurname, king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfSourceSurname Context triple: [Ong, meaningOfSourceSurname, king]
-
A.
hasSurnameEthymology
Indicates that an entity’s surname originates from, or is derived based on, a specified source, language, or etymological root.
-
B.
originalNameMeaningSource
chosen
Indicates that there is a source or reference that explains or provides the meaning of an entity’s original name.
-
C.
hasAncestralFamilyNameMeaning
Indicates that an entity’s ancestral family name carries a specific meaning or significance.
-
D.
nameOriginExplanation
Indicates that an explanation is provided for the origin or derivation of a given name.
-
E.
familyNameDerivedFrom
Indicates that one entity’s family name originates from, or is etymologically derived from, 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 3:01 a.m.