Triple
T30938373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPA |
E788187
|
entity |
| Predicate | lastSignificantActivity |
P40296
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [UPA, lastSignificantActivity, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastSignificantActivity Context triple: [UPA, lastSignificantActivity, 1950s]
-
A.
likelyLastActivity
Indicates that an activity is inferred to be the most recent or final action performed by an entity within a given context or timeframe.
-
B.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
-
C.
hasEvidenceOfActivitySince
Indicates that there is evidence showing an entity has been active or engaged in some activity from a specified point in time onward.
-
D.
lastKnownActivity
chosen
Indicates the most recent recorded action, event, or state associated with an entity.
-
E.
hasRecentActivity
Indicates that the subject has performed an action or been involved in an event within a defined recent time period.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:52 p.m.