Triple
T35339756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furthur (Merry Pranksters bus) |
E1020563
|
entity |
| Predicate | hasWordOnDestinationSign |
P144674
|
FINISHED |
| Object | Furthur |
—
|
NE NERFINISHED |
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: Furthur | Statement: [Furthur (Merry Pranksters bus), hasWordOnDestinationSign, Furthur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWordOnDestinationSign Context triple: [Furthur (Merry Pranksters bus), hasWordOnDestinationSign, Furthur]
-
A.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
B.
hasConsonantSigns
Indicates that one entity possesses or includes consonant sign characters as part of its representation or structure.
-
C.
hasLogographicSign
Indicates that an entity is associated with or represented by a logographic sign (a written symbol that stands for a word or morpheme).
-
D.
hasMeaningInOriginLanguage
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning in its original or source language.
-
E.
hasSignageLetter
chosen
Indicates that an object or location bears signage containing a specific letter or set of letters.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 3, 2026, 4:03 p.m.