Triple
T30356966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Wonder |
E772170
|
entity |
| Predicate | isPersonaIn |
P61233
|
FINISHED |
| Object | Wonder Bar narrative or venue |
—
|
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: Wonder Bar narrative or venue | Statement: [Al Wonder, isPersonaIn, Wonder Bar narrative or venue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPersonaIn Context triple: [Al Wonder, isPersonaIn, Wonder Bar narrative or venue]
-
A.
hasPersona
chosen
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
-
B.
isPersonalNameIn
Indicates that a personal name appears within or is contained in a specified context, such as a document, text span, or dataset.
-
C.
isFictionalPersonFrom
Indicates that a fictional person originates from or is associated with a particular place or source.
-
D.
isPer
Indicates that the subject entity is classified as a person.
-
E.
isPersonalName
Indicates that the value is a personal name identifying an individual person.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6823fe8c48190a8911627f79dd949 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:57 p.m.