Triple
T33649217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Sam |
E862044
|
entity |
| Predicate | hasFunnelType |
P177639
|
FINISHED |
| Object | special funnel |
—
|
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: special funnel | Statement: [Peter Sam, hasFunnelType, special funnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunnelType Context triple: [Peter Sam, hasFunnelType, special funnel]
-
A.
hasFunnels
Indicates that one entity possesses or is equipped with one or more funnels associated with another entity or context.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
numberOfFunnels
Indicates the quantity of funnels associated with or present on a given entity.
-
D.
hasFillingType
Indicates that an entity is associated with a specific type or category of filling it contains or uses.
-
E.
hasFilterType
Indicates that an entity is associated with, or constrained by, a specific type or category of filter applied to it.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:42 a.m.