Triple
T18386269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3A |
E446599
|
entity |
| Predicate | hasLetterSuffix |
P130930
|
FINISHED |
| Object | A |
—
|
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: A | Statement: [3A, hasLetterSuffix, A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLetterSuffix Context triple: [3A, hasLetterSuffix, A]
-
A.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
B.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
-
C.
hasLetterPattern
Indicates that one entity exhibits or matches a specific sequence or arrangement of letters defined by another entity.
-
D.
hasAdditionalLetters
Indicates that one entity contains extra or more letters than another entity, beyond a specified base set or reference.
-
E.
hasNameSuffix
Indicates that an entity’s name includes a specific suffix or ending component.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e517a00c608190a8f0010c7b53df90 |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:46 a.m.