Triple
T30675251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinite Comics |
E780892
|
entity |
| Predicate | usedToTieInWith |
P133150
|
FINISHED |
| Object | major Marvel crossover events |
—
|
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: major Marvel crossover events | Statement: [Infinite Comics, usedToTieInWith, major Marvel crossover events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToTieInWith Context triple: [Infinite Comics, usedToTieInWith, major Marvel crossover events]
-
A.
tieInWith
chosen
Indicates that one thing is connected, coordinated, or made consistent with another, often as part of a combined plan, theme, or schedule.
-
B.
tiedTo
Indicates that one entity is physically or figuratively fastened, bound, or otherwise constrained in connection to another entity.
-
C.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
D.
usedToBePartOf
Indicates that an entity was formerly a component or member of another entity but is no longer part of it.
-
E.
usesTwoLeggedTies
Indicates that one entity employs or applies two-legged ties in relation to another entity or context.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 8:32 p.m.