Triple
T35339748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furthur (Merry Pranksters bus) |
E1020563
|
entity |
| Predicate | hasDestinationSignText |
P9766
|
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), hasDestinationSignText, Furthur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDestinationSignText Context triple: [Furthur (Merry Pranksters bus), hasDestinationSignText, Furthur]
-
A.
hasSign
chosen
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
B.
hasSignCode
Indicates that an entity is associated with a specific sign identifier or code used to represent it.
-
C.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
D.
hasSignConvention
Indicates that a particular system, quantity, or representation follows a specified rule for assigning positive and negative signs.
-
E.
hasSignagePrefix
Indicates that one signage element begins with or contains another signage element as its initial segment or prefix.
- 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_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
Created at: May 3, 2026, 4:03 p.m.