Triple
T26088870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadpool Corps |
E658061
|
entity |
| Predicate | hasLimitedSeries |
P172333
|
FINISHED |
| Object | Deadpool Corps |
—
|
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: Deadpool Corps | Statement: [Deadpool Corps, hasLimitedSeries, Deadpool Corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedSeries Context triple: [Deadpool Corps, hasLimitedSeries, Deadpool Corps]
-
A.
hasLimitedEditionSeries
Indicates that an entity is associated with a special, restricted-quantity series or collection.
-
B.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
C.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
D.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
E.
hasLimitingSequence
Indicates that one entity serves as a limiting sequence (in the sense of convergence or approximation) for another entity.
- F. None of above. chosen
Provenance (4 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 26, 2026, 7:45 p.m.