Triple
T15217150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUSIP |
E363664
|
entity |
| Predicate | hasNextTwoCharactersMeaning |
P117561
|
FINISHED |
| Object | issue identifier |
—
|
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: issue identifier | Statement: [CUSIP, hasNextTwoCharactersMeaning, issue identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNextTwoCharactersMeaning Context triple: [CUSIP, hasNextTwoCharactersMeaning, issue identifier]
-
A.
hasTwinCharacters
Indicates that two characters are twins, sharing the same parents and birth time or very close birth times.
-
B.
hasSignificantCharacter
Indicates that an entity possesses a character or trait that is notably important, influential, or central within a given context.
-
C.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
D.
hasLanguageCharacter
Indicates that an entity uses, contains, or is associated with a specific written or symbolic character from a language.
-
E.
hasMiddleMovementCharacter
Indicates that a musical work’s middle movement features a specified character or quality (e.g., mood, style, or expressive trait).
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0076f90c481909989befe031a2cae |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:11 a.m.