Triple
T37997539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvel One-Shots |
E947999
|
entity |
| Predicate | notableShortLedToSeries |
P204527
|
FINISHED |
| Object | Agent Carter |
E280721
|
NE 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: Agent Carter | Statement: [Marvel One-Shots, notableShortLedToSeries, Agent Carter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableShortLedToSeries Context triple: [Marvel One-Shots, notableShortLedToSeries, Agent Carter]
-
A.
notableOriginalSeries
Indicates that an entity is recognized as a significant or distinguished original series associated with another entity (such as a platform, creator, or franchise).
-
B.
notableSeries
Indicates that an entity is a significant or well-known installment within a particular series or franchise.
-
C.
notableShort
Indicates that an entity is notably short in height or duration compared to typical or expected standards.
-
D.
notableEpisode
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
-
E.
notableSeriesFocus
Indicates that a notable series primarily centers on, highlights, or is thematically focused around a particular subject or entity.
- F. None of above. chosen
Provenance (5 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4167fc29bc8190969f1dade62f6c3b |
completed | June 28, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:20 p.m.