Triple
T34383101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeong |
E882487
|
entity |
| Predicate | positionInTwoSyllableName |
P1082
|
FINISHED |
| Object | first syllable |
—
|
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: first syllable | Statement: [Jeong, positionInTwoSyllableName, first syllable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTwoSyllableName Context triple: [Jeong, positionInTwoSyllableName, first syllable]
-
A.
namePosition
chosen
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
B.
secondSyllable
Indicates that the second syllable of one linguistic unit corresponds to, matches, or is identified as a particular syllable or sound in relation to another entity.
-
C.
hasSyllablesForNames
Indicates that there is an association between names and the syllables that compose or are used to form those names.
-
D.
positionInDuo
Indicates the specific role or placement an entity holds within a two-member grouping or partnership.
-
E.
positionOfNamesake
Indicates that one entity occupies the role, rank, or spatial/organizational position associated with another entity for which it is named.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: May 1, 2026, 1:59 a.m.