Triple
T31317073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Belong with Me |
E798624
|
entity |
| Predicate | centralLine |
P190063
|
FINISHED |
| Object | You belong with me |
—
|
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: You belong with me | Statement: [You Belong with Me, centralLine, You belong with me]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralLine Context triple: [You Belong with Me, centralLine, You belong with me]
-
A.
линия
Indicates a relationship where something is a line or forms a linear connection or boundary between points or areas.
-
B.
criticalLine
Indicates that one entity is a crucial or decisive line (such as a boundary, path, or threshold) whose state or position significantly affects the other entity or overall system.
-
C.
enteredCentralLineService
Indicates that an entity has begun receiving or providing central line–related medical services or procedures.
-
D.
centralStripePosition
Indicates the relative location or alignment of a central stripe within or on an object.
-
E.
secondaryLine
Indicates that something serves as a secondary or auxiliary line in relation to a primary or main line.
- F. None of above. chosen
Provenance (4 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: April 29, 2026, 9:15 p.m.