Triple
T37229002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spot the cat |
E923079
|
entity |
| Predicate | oftenMoreCompetentThan |
P103396
|
FINISHED |
| Object | Hong Kong Phooey |
—
|
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: Hong Kong Phooey | Statement: [Spot the cat, oftenMoreCompetentThan, Hong Kong Phooey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenMoreCompetentThan Context triple: [Spot the cat, oftenMoreCompetentThan, Hong Kong Phooey]
-
A.
morePrestigiousThan
Indicates that one entity is regarded as having higher status, esteem, or prestige than another.
-
B.
notCompetentFor
Indicates that an entity lacks the necessary ability, qualification, or suitability to perform or handle another specified entity or task.
-
C.
oftenOutsmarts
chosen
Indicates that one entity frequently surpasses or outwits another in intelligence, strategy, or problem-solving.
-
D.
strongerAt
Indicates that one entity has greater strength, power, or effectiveness than another in a specified context, condition, or domain.
-
E.
moreAdaptiveThan
Indicates that one entity is better able to adjust or respond effectively to changes or varying conditions than another entity.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 3, 2026, 4:15 p.m.