Triple
T33632357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ash Morgan |
E861598
|
entity |
| Predicate | partOfFictionalTeam |
P75242
|
FINISHED |
| Object | Hustle crew |
—
|
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: Hustle crew | Statement: [Ash Morgan, partOfFictionalTeam, Hustle crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfFictionalTeam Context triple: [Ash Morgan, partOfFictionalTeam, Hustle crew]
-
A.
partOfFictionalGroup
chosen
Indicates that an entity belongs to or is a member of a specific fictional group, organization, or team.
-
B.
fictionalTeam
Indicates that the related entities are members of, or otherwise associated with, the same fictional team within a narrative or imaginary context.
-
C.
divisionOfFictionalTeam
Indicates that a fictional team belongs to or competes within a specific division or grouping in its fictional context.
-
D.
portraysFictionalTeam
Indicates that one entity depicts or represents a fictional team within a work or medium.
-
E.
hasFictionalMember
Indicates that a group, organization, or collection includes at least one member that is fictional rather than real.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 1, 2026, 1:41 a.m.