Triple
T33869179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluto |
E868148
|
entity |
| Predicate | basedOnOrRelatedTo |
P195279
|
FINISHED |
| Object | Brutus (Popeye character) |
—
|
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: Brutus (Popeye character) | Statement: [Bluto, basedOnOrRelatedTo, Brutus (Popeye character)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnOrRelatedTo Context triple: [Bluto, basedOnOrRelatedTo, Brutus (Popeye character)]
-
A.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
B.
basedOnSubjectOf
Indicates that something is derived from, informed by, or constructed using the subject matter or content of another entity.
-
C.
basedOnOrSourceFor
chosen
Indicates that one entity is derived from, influenced by, or used as the originating source for another entity.
-
D.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
E.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 1:47 a.m.