Triple
T34672634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pom |
E890415
|
entity |
| Predicate | hasNotableUsageThrough |
P101325
|
FINISHED |
| Object | Marvel Cinematic Universe |
E118193
|
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: Marvel Cinematic Universe | Statement: [Pom, hasNotableUsageThrough, Marvel Cinematic Universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableUsageThrough Context triple: [Pom, hasNotableUsageThrough, Marvel Cinematic Universe]
-
A.
hasNotableUsageRegion
Indicates that something is prominently or distinctively used within a particular geographic region.
-
B.
hasUsageNote
Indicates that there is an associated explanatory note describing how or when something should be used.
-
C.
hasNotableUseExample
chosen
Indicates that there exists a particularly significant or illustrative example of how something is used.
-
D.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
E.
hasHistoricalUsageIn
Indicates that something has been used or practiced within a particular historical period, context, or tradition.
- F. None of above.
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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0337c7389c8190b71d27b8eb8daf9a |
completed | May 12, 2026, 2:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3749079fdc81908004d7a554eebd5f |
completed | June 21, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a0335b7b1588190b02a0ce6a08704aa |
completed | May 12, 2026, 2:14 p.m. |
Created at: May 1, 2026, 2:05 a.m.