Triple
T1351843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Made to Love |
E28898
|
entity |
| Predicate | isTrackNumber |
P7270
|
FINISHED |
| Object | 2 on standard edition of Love in the Future |
—
|
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: 2 on standard edition of Love in the Future | Statement: [Made to Love, isTrackNumber, 2 on standard edition of Love in the Future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTrackNumber Context triple: [Made to Love, isTrackNumber, 2 on standard edition of Love in the Future]
-
A.
trackNumberOnAlbum
chosen
Indicates the specific position or sequence number that a track occupies on an album.
-
B.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
C.
numberOfTracks
Indicates the quantity of tracks associated with a given entity.
-
D.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
E.
trackType
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26b1b4881908ae4b1b2c9b268a0 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.