Triple
T34948336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSC |
E1007913
|
entity |
| Predicate | predecessorStandardAbbreviation |
P29210
|
FINISHED |
| Object | AACR |
—
|
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: AACR | Statement: [JSC, predecessorStandardAbbreviation, AACR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorStandardAbbreviation Context triple: [JSC, predecessorStandardAbbreviation, AACR]
-
A.
shortNameOfPredecessor
Indicates that an entity has a predecessor whose abbreviated or shorter name is being specified.
-
B.
previousAbbreviation
chosen
Indicates that one abbreviation was used earlier or previously in place of another for the same entity or term.
-
C.
abbreviationOfSuccessor
Indicates that one entity is an abbreviation or shortened form of another entity that is the successor in some sequence or versioning.
-
D.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
E.
predecessorCode
Indicates that one code directly precedes another code in a defined sequence or versioning order.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4 p.m.