Triple
T30598002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civil War (2015) |
E778835
|
entity |
| Predicate | hasIssueTitle |
P65893
|
FINISHED |
| Object | Civil War (2015) #1 |
—
|
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: Civil War (2015) #1 | Statement: [Civil War (2015), hasIssueTitle, Civil War (2015) #1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIssueTitle Context triple: [Civil War (2015), hasIssueTitle, Civil War (2015) #1]
-
A.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
B.
issuesTitle
Indicates that an entity formally grants or assigns an official title or designation to another entity.
-
C.
containsIssue
Indicates that one entity includes, encompasses, or has within it a particular issue, problem, or defect.
-
D.
hasTitleIn
chosen
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
hadTitle
Indicates that an entity held or was assigned a specific title or formal designation.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 8:24 p.m.