Triple
T25278784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweetback |
E633771
|
entity |
| Predicate | hasCoreTrio |
P20032
|
FINISHED |
| Object | Stuart Matthewman, Paul S. Denman, Andrew Hale |
—
|
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: Stuart Matthewman, Paul S. Denman, Andrew Hale | Statement: [Sweetback, hasCoreTrio, Stuart Matthewman, Paul S. Denman, Andrew Hale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreTrio Context triple: [Sweetback, hasCoreTrio, Stuart Matthewman, Paul S. Denman, Andrew Hale]
-
A.
hasCore
Indicates that one entity possesses, contains, or is built around a central or most essential component represented by another entity.
-
B.
hasCoreUnit
Indicates that an entity includes or is composed around a primary, central, or fundamental unit.
-
C.
hasCompanionCore
Indicates that an entity is associated with, or accompanied by, a specific companion core.
-
D.
hasCoreMember
chosen
Indicates that an entity includes another entity as a central or primary member of its group, organization, or structure.
-
E.
hasCorePower
Indicates that an entity possesses a primary or fundamental power, ability, or capability that defines its essential function or role.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:18 p.m.