Triple
T32555026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Get Down |
E832073
|
entity |
| Predicate | setInFictionalGroup |
P104242
|
FINISHED |
| Object | The Get Down Brothers |
—
|
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: The Get Down Brothers | Statement: [The Get Down, setInFictionalGroup, The Get Down Brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInFictionalGroup Context triple: [The Get Down, setInFictionalGroup, The Get Down Brothers]
-
A.
setInFictionalOrganization
Indicates that an entity is located within, associated with, or takes place inside a fictional organization.
-
B.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
-
C.
associatedWithFictionalGroup
chosen
Indicates that an entity has a connection or affiliation with a fictional group, organization, or collective.
-
D.
setInFictionalizedRegionOf
Indicates that an event or narrative is located within a region that is a fictionalized or altered version of a real-world place.
-
E.
setInFictionalUniversity
Indicates that the events or narrative take place within the setting of a fictional university.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:03 a.m.