Triple
T16296848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SN 1961V |
E395668
|
entity |
| Predicate | eventTypeStatus |
P110998
|
FINISHED |
| Object | disputed |
—
|
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: disputed | Statement: [SN 1961V, eventTypeStatus, disputed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventTypeStatus Context triple: [SN 1961V, eventTypeStatus, disputed]
-
A.
eventStatus
chosen
Indicates the current state or phase of an event within its lifecycle (e.g., planned, ongoing, completed, or canceled).
-
B.
statusChange
Indicates a transition in an entity’s state or condition from one status to another over time.
-
C.
campaignStatus
Indicates the current state or phase of a campaign within its lifecycle (e.g., planned, active, paused, or completed).
-
D.
actStatus
Indicates the current state or condition of an action or event, such as whether it is planned, ongoing, completed, or cancelled.
-
E.
participantStatus
Indicates the role, condition, or level of involvement that a participant has within a specific event, process, or relationship.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2dcdac819083918f0964dd5666 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.