Triple
T27810798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurebesh |
E702512
|
entity |
| Predicate | hasLetterSet |
P17387
|
FINISHED |
| Object | Aurek |
—
|
NE NERFINISHED |
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: Aurek | Statement: [Aurebesh, hasLetterSet, Aurek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLetterSet Context triple: [Aurebesh, hasLetterSet, Aurek]
-
A.
hasLetter
chosen
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
B.
hasLettersFor
Indicates that one entity possesses or contains written correspondence intended for another entity.
-
C.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
-
D.
hasLetterCount
Indicates that an entity is associated with a specific number representing how many letters it contains.
-
E.
hasLetterPattern
Indicates that one entity exhibits or matches a specific sequence or arrangement of letters defined by another entity.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 5:42 p.m.