Triple
T35274773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live From the Gutter |
E1018766
|
entity |
| Predicate | isJointProjectTrackOf |
P26119
|
FINISHED |
| Object | Future |
—
|
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: Future | Statement: [Live From the Gutter, isJointProjectTrackOf, Future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJointProjectTrackOf Context triple: [Live From the Gutter, isJointProjectTrackOf, Future]
-
A.
isSisterProjectOf
Indicates that two projects are related and aligned in purpose or scope, typically operating in parallel under a common umbrella or organization.
-
B.
isOnProjectBy
Indicates that an entity is assigned to or working on a project under the responsibility or authorship of another entity.
-
C.
hasJointProgramWith
Indicates that two entities collaborate to offer a shared or coordinated program, initiative, or course of study.
-
D.
isTrackedBy
chosen
Indicates that an entity’s state, behavior, or changes are being monitored, recorded, or followed by another entity.
-
E.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fa3865c8190a697c0dba4c37bb8 |
completed | May 3, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.