Triple
T34562035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Know That You Know |
E887369
|
entity |
| Predicate | hasBeenRecordedAs |
P9348
|
FINISHED |
| Object | instrumental |
—
|
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: instrumental | Statement: [I Know That You Know, hasBeenRecordedAs, instrumental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenRecordedAs Context triple: [I Know That You Know, hasBeenRecordedAs, instrumental]
-
A.
mayBeRecordedAs
Indicates that something can optionally be documented or stored in a recorded form, but is not required to be.
-
B.
reRecordedWith
Indicates that an existing recording was made again in collaboration with the specified entity (such as an artist, group, or producer).
-
C.
areRecordedBy
Indicates that an event, observation, or piece of information is captured or documented by a specific recording agent, device, or process.
-
D.
recorded
chosen
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
E.
hasRe-recording
Indicates that one recording is a new or updated version made again from the same original material or performance.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 2:02 a.m.