Triple
T36349453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remember Sammy Jankis |
E895154
|
entity |
| Predicate | hasQuotationForm |
P155388
|
FINISHED |
| Object | "Remember Sammy Jankis" |
—
|
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: "Remember Sammy Jankis" | Statement: [Remember Sammy Jankis, hasQuotationForm, "Remember Sammy Jankis"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuotationForm Context triple: [Remember Sammy Jankis, hasQuotationForm, "Remember Sammy Jankis"]
-
A.
hasQuotationSystem
Indicates that an entity uses or is associated with a particular system or convention for representing quotations.
-
B.
hasQuotationStatus
Indicates that an entity has a particular quotation-related state or condition (such as being quoted, unquoted, or having a specific quotation status).
-
C.
containsQuotationMarks
chosen
Indicates that the referenced text includes one or more quotation mark characters within it.
-
D.
hasObligationForm
Indicates that one entity is required to use or comply with a specific formal document, format, or procedure as part of an obligation.
-
E.
hasCitationForm
Indicates that an entity is associated with a specific standardized form used for citing or referencing it.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:09 p.m.