Triple
T22859811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ambroise |
E566884
|
entity |
| Predicate | hasLetterforms |
P150002
|
FINISHED |
| Object | elegant |
—
|
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: elegant | Statement: [Ambroise, hasLetterforms, elegant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLetterforms Context triple: [Ambroise, hasLetterforms, elegant]
-
A.
hasDistinctLetterForms
Indicates that the related writing system or symbol set uses different visual shapes or styles for the same letter in different contexts (such as position, case, or usage).
-
B.
hasLetterType
Indicates that an entity is associated with or classified by a specific type or category of letter.
-
C.
hasContextualLetterForms
Indicates that the written form of a letter changes shape depending on its surrounding characters or position within a word.
-
D.
characterFormationMethod
Indicates the process or technique by which a character is created, developed, or brought into existence.
-
E.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ec082c08190943e6cfc2e25c5cc |
completed | April 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:37 p.m.