Triple
T37266445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Gazoo |
E924397
|
entity |
| Predicate | oftenAppearsTo |
P177012
|
FINISHED |
| Object | Fred Flintstone |
—
|
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: Fred Flintstone | Statement: [The Great Gazoo, oftenAppearsTo, Fred Flintstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenAppearsTo Context triple: [The Great Gazoo, oftenAppearsTo, Fred Flintstone]
-
A.
appearTo
Indicates that something gives the impression or seems to be a certain way to an observer, without confirming that it actually is so.
-
B.
mayAppear
Indicates that an entity is allowed or has the possibility to be present or occur in association with another entity or context.
-
C.
frequentlySeen
chosen
Indicates that one entity is observed or encountered many times or on a regular basis in relation to another entity.
-
D.
oftenFrom
Indicates that something frequently originates, derives, or comes from a particular source or location.
-
E.
oftenSays
Indicates that one entity frequently makes a particular statement or remark, or regularly expresses a certain idea or phrase.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: May 3, 2026, 4:15 p.m.