Triple
T30361179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Promise box set |
E772289
|
entity |
| Predicate | featuresRecordingSessionsLocation |
P8088
|
FINISHED |
| Object | New Jersey |
—
|
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: New Jersey | Statement: [The Promise box set, featuresRecordingSessionsLocation, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRecordingSessionsLocation Context triple: [The Promise box set, featuresRecordingSessionsLocation, New Jersey]
-
A.
recordingLocationTour
Indicates the place where a tour-related recording (such as a live performance or tour event) was made.
-
B.
sharesRecordingSessionsWith
Indicates that two entities have participated together in one or more of the same recording sessions.
-
C.
placeOfRecording
chosen
Indicates the location where an audio, video, or other recording was made.
-
D.
captureLocation
Indicates the place where an entity or event is captured, recorded, or taken.
-
E.
recordedAtMultipleLocations
Indicates that the same event, action, or data instance was recorded or captured at more than one distinct location.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
Created at: April 29, 2026, 7:58 p.m.