Triple
T1210691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taegeukgi |
E25991
|
entity |
| Predicate | upperLeftTrigram |
P24700
|
FINISHED |
| Object | geon |
—
|
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: geon | Statement: [Taegeukgi, upperLeftTrigram, geon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperLeftTrigram Context triple: [Taegeukgi, upperLeftTrigram, geon]
-
A.
cornerOfTriangle
Indicates that the subject is a vertex (corner point) belonging to a specific triangle.
-
B.
above
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
C.
hasThreeLetterForm
Indicates that an entity’s written or symbolic form consists of exactly three letters.
-
D.
firstLetter
Indicates that one entity is the initial character or starting letter of another entity (typically a string or word).
-
E.
usesTrigraph
Indicates that one entity employs or incorporates a trigraph (a three-character sequence representing a single unit, such as a sound or symbol) in relation to another entity or context.
- F. None of above. chosen
Provenance (4 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bde4670481908c16a3a8c1a54aad |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:46 p.m.