Triple
T31646354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SML/NJ |
E807593
|
entity |
| Predicate | hasAbbreviationForName |
P45686
|
FINISHED |
| Object | Standard ML of New Jersey |
—
|
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: Standard ML of New Jersey | Statement: [SML/NJ, hasAbbreviationForName, Standard ML of New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbbreviationForName Context triple: [SML/NJ, hasAbbreviationForName, Standard ML of New Jersey]
-
A.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
B.
isAbbreviation
chosen
Indicates that one term is a shortened or abbreviated form of another term.
-
C.
hasAbbreviationStatus
Indicates that an entity has a particular status or condition regarding its abbreviation (e.g., whether it is abbreviated, how, or to what extent).
-
D.
hasAbbreviationStyleName
Indicates that an entity is associated with a specific style or form of its abbreviated name.
-
E.
hasAbbreviationPattern
Indicates that there is a systematic abbreviation relationship between two strings, where one follows a recognizable pattern derived from the other.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a91f65548190b598917dada0c2c0 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:51 p.m.