Triple
T2545888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Not-a-Flamethrower |
E57900
|
entity |
| Predicate | nameStyle |
P39478
|
FINISHED |
| Object | humorous |
—
|
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: humorous | Statement: [Not-a-Flamethrower, nameStyle, humorous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameStyle Context triple: [Not-a-Flamethrower, nameStyle, humorous]
-
A.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
B.
namePosition
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
C.
namesakeFullName
Indicates that one entity’s full name is used as the namesake or source of the name for another entity.
-
D.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
E.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2c285288190b41fc0188879623a |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:47 p.m.