Triple
T9590005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KPW |
E231391
|
entity |
| Predicate | formatConvention |
P78044
|
FINISHED |
| Object | amount precedes symbol in local usage |
—
|
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: amount precedes symbol in local usage | Statement: [KPW, formatConvention, amount precedes symbol in local usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatConvention Context triple: [KPW, formatConvention, amount precedes symbol in local usage]
-
A.
conventionFor
chosen
Indicates a relationship where something serves as a standard, rule, or customary practice governing how another thing is done, represented, or interpreted.
-
B.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
C.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
D.
logicConvention
Indicates a relationship where entities participate in or are associated with a convention, event, or standard related to logic or logical systems.
-
E.
signingConvention
Indicates that one party formally agrees to and adopts the terms of a convention, treaty, or formal agreement.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99f32e688190bb13bccfa5031f16 |
completed | April 1, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.