Triple
T12005313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aftermath |
E285764
|
entity |
| Predicate | hasUSVersion |
P7228
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aftermath, hasUSVersion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUSVersion Context triple: [Aftermath, hasUSVersion, true]
-
A.
hasUSAN
Indicates that an entity has a specified United States Adopted Name (USAN), typically a nonproprietary name assigned to a pharmaceutical substance.
-
B.
hasInternationalVersion
chosen
Indicates that an entity has a corresponding version or counterpart adapted for use in multiple countries or international contexts.
-
C.
hasNetworkUS
Indicates that an entity possesses, operates, or is associated with a network located in or serving the United States.
-
D.
isInUnitedStates
Indicates that one entity is located within the geographic or political boundaries of the United States.
-
E.
USProvides
Indicates that the United States supplies, furnishes, or makes available something (such as aid, resources, services, or support) to another entity.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c481a48190b311d6809808ef1b |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.