Triple
T4337767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Over and Over |
E97504
|
entity |
| Predicate | isCrossoverSingle |
P3282
|
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: [Over and Over, isCrossoverSingle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCrossoverSingle Context triple: [Over and Over, isCrossoverSingle, true]
-
A.
crossesOverWith
Indicates that one entity intersects or overlaps with another, typically by passing across or through its path, boundary, or extent.
-
B.
isOnlyDirectCrossingBetween
Indicates that one entity serves as the sole direct crossing (e.g., bridge, passage, or connection) between two other entities, with no alternative direct crossing available.
-
C.
hasSingle
chosen
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
-
D.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
E.
crossedWith
Indicates that one entity has moved from one side of another entity or boundary to the opposite side, typically by passing over or through it.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3516c621881909f094d040d4805e9 |
completed | March 12, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69b34f4fe1c481908d6d66e15697c04b |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:14 p.m.