Triple
T31154265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Star Batman & Robin, the Boy Wonder |
E794158
|
entity |
| Predicate | plannedIssueCount |
P31088
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [All-Star Batman & Robin, the Boy Wonder, plannedIssueCount, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedIssueCount Context triple: [All-Star Batman & Robin, the Boy Wonder, plannedIssueCount, 12]
-
A.
numberPlanned
Indicates that a specific quantity has been scheduled or intended for a future action or allocation.
-
B.
numberOfIssues
chosen
Indicates the quantity of issues associated with a given entity or context.
-
C.
numberOfRulesPlanned
Indicates the planned or intended count of rules associated with an entity or process.
-
D.
hasPlanningIssue
Indicates that an entity is associated with a problem, concern, or complication related to planning or plan formulation.
-
E.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 29, 2026, 9:06 p.m.