Triple
T15415969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Been Around tha World |
E369230
|
entity |
| Predicate | isRecordedInStudio |
P86545
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Been Around tha World, isRecordedInStudio, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecordedInStudio Context triple: [Been Around tha World, isRecordedInStudio, yes]
-
A.
recordedForStudio
Indicates that a recording was made specifically for, or under contract with, a particular studio.
-
B.
isStudioRecording
chosen
Indicates that the recording was made in a controlled studio environment rather than in a live or field setting.
-
C.
isRecordedMusic
Indicates that something is music that has been captured and stored in a recorded form, rather than being performed live in the moment.
-
D.
hasRecordingStudio
Indicates that an entity possesses, operates, or is associated with a recording studio.
-
E.
wasRecordedIn
Indicates that an event, action, or piece of information was documented or captured within a specific record, medium, or recording session.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ea8a8a081909749db1b29d85fcc |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.