Triple
T8266953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fab Five |
E193323
|
entity |
| Predicate | memberPosition |
P47236
|
FINISHED |
| Object | Chris Webber – power forward |
—
|
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: Chris Webber – power forward | Statement: [Fab Five, memberPosition, Chris Webber – power forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberPosition Context triple: [Fab Five, memberPosition, Chris Webber – power forward]
-
A.
clubPosition
chosen
Indicates the specific role or position an individual holds within a sports club or team.
-
B.
ownerPosition
Indicates the spatial or positional relationship of an owner relative to the owned entity.
-
C.
memberTitle
Indicates the formal title or designation held by a member within a group, organization, or body.
-
D.
memberRepresents
Indicates that one entity serves as an official representative or delegate acting on behalf of another entity within a group, organization, or body.
-
E.
boardMember
Indicates that a person serves on the governing board of an organization, participating in its oversight and decision-making.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb794e6880819084dff5df42332835 |
completed | March 31, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69cb36b8707881909aca349230495a5a |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:50 p.m.