Triple
T4323438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | What Are We Doin' in Love |
E96574
|
entity |
| Predicate | crossoverHit |
P56239
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [What Are We Doin' in Love, crossoverHit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossoverHit Context triple: [What Are We Doin' in Love, crossoverHit, true]
-
A.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
B.
bestCrossed
Indicates that one entity has surpassed or exceeded another in a crossing-related context, such as achieving the most successful or optimal crossing among alternatives.
-
C.
crossesOverWith
Indicates that one entity intersects or overlaps with another, typically by passing across or through its path, boundary, or extent.
-
D.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
E.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35118abe481908b7987019be217e1 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:13 p.m.