Triple
T37701924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tono |
E939085
|
entity |
| Predicate | conventionality |
P191625
|
FINISHED |
| Object | nonstandard |
—
|
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: nonstandard | Statement: [Tono, conventionality, nonstandard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conventionality Context triple: [Tono, conventionality, nonstandard]
-
A.
conventionFor
Indicates a relationship where something serves as a standard, rule, or customary practice governing how another thing is done, represented, or interpreted.
-
B.
associatedConvention
Indicates a relationship where something is linked or connected to a particular convention (such as an event, standard, or formal gathering).
-
C.
reasonForConvention
Indicates the underlying purpose, cause, or motivation that led to holding a particular convention.
-
D.
governingConvention
Indicates that one entity is the formal agreement, treaty, or convention that provides the authoritative rules or framework governing another entity or activity.
-
E.
conventionSigned
Indicates that an entity has formally agreed to and signed a specific convention or treaty.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.