Triple
T33648387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward the Blue Engine |
E862023
|
entity |
| Predicate | hasFunnel |
P171623
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Edward the Blue Engine, hasFunnel, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunnel Context triple: [Edward the Blue Engine, hasFunnel, yes]
-
A.
hasFunnels
chosen
Indicates that one entity possesses or is equipped with one or more funnels associated with another entity or context.
-
B.
numberOfFunnels
Indicates the quantity of funnels associated with or present on a given entity.
-
C.
hasFlux
Indicates that one entity exhibits or is characterized by a flow, rate of transfer, or continuous change with respect to another entity or quantity.
-
D.
hasFolly
Indicates that an entity possesses or exhibits a foolish, ill-judged, or irrational quality, behavior, or decision.
-
E.
hasTrough
Indicates that one entity possesses, includes, or is characterized by a trough, such as a long, narrow, typically low or recessed feature or container.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.