Triple
T19091180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Losers (Vertigo) |
E467285
|
entity |
| Predicate | imprintLine |
P134336
|
FINISHED |
| Object | Vertigo mature readers line |
—
|
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: Vertigo mature readers line | Statement: [The Losers (Vertigo), imprintLine, Vertigo mature readers line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imprintLine Context triple: [The Losers (Vertigo), imprintLine, Vertigo mature readers line]
-
A.
imprintedOn
Indicates that one entity has formed a strong, often early-life, attachment or bond to another entity, typically treating it as a primary reference or caregiver.
-
B.
imprintsOn
Indicates that one entity forms a strong, often instinctive or formative attachment or bond to another, typically as a primary reference or guide.
-
C.
hadImprint
Indicates that one entity bears or once bore a physical or symbolic mark, stamp, or impression produced by another entity.
-
D.
inscriptionIncludesLine
Indicates that an inscription contains a specific line of text as one of its components.
-
E.
writingLine
Indicates that one entity is writing or drawing a line, typically marking or inscribing a linear trace on a surface.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34b6b348190bb868356ed8b655a |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.