Triple
T4222692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SENĆOŦEN |
E94378
|
entity |
| Predicate | hasSpecialCharacters |
P2271
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SENĆOŦEN, hasSpecialCharacters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialCharacters Context triple: [SENĆOŦEN, hasSpecialCharacters, yes]
-
A.
hasSpecialCharacter
chosen
Indicates that a given entity (such as a string or identifier) contains at least one non-alphanumeric special character.
-
B.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
C.
containsCharacter
Indicates that one entity includes a specific character as part of its content or composition.
-
D.
hasDistinctCharacterSet
Indicates that two compared items use different sets of characters, with no character set being a subset or duplicate of the other.
-
E.
hasSpecials
Indicates that an entity offers or is associated with special deals, promotions, or limited-time offers.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.