Triple
T22678155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs Eaves |
E560402
|
entity |
| Predicate | openTypeFeatures |
P9191
|
FINISHED |
| Object | discretionary ligatures |
—
|
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: discretionary ligatures | Statement: [Mrs Eaves, openTypeFeatures, discretionary ligatures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openTypeFeatures Context triple: [Mrs Eaves, openTypeFeatures, discretionary ligatures]
-
A.
OTypeCharacteristic
Indicates that an entity has a specific characteristic or property related to its type.
-
B.
hasLigatures
chosen
Indicates that one writing system, font, or text includes combined character forms (ligatures) that join two or more individual glyphs into a single symbol.
-
C.
inkFeatures
Indicates that an entity possesses specific ink-related characteristics or properties.
-
D.
writingSystemFeatures
Indicates the specific structural or functional characteristics that define how a particular writing system represents language.
-
E.
spanFeature
Indicates a relationship where a feature or characteristic extends across or covers a specified span or interval.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785d93e48190b37d11642b0cb123 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:11 p.m.