Triple
T25917767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beck Oliver |
E653078
|
entity |
| Predicate | crossoverAppearanceIn |
P8704
|
FINISHED |
| Object | iCarly |
—
|
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: iCarly | Statement: [Beck Oliver, crossoverAppearanceIn, iCarly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossoverAppearanceIn Context triple: [Beck Oliver, crossoverAppearanceIn, iCarly]
-
A.
crossoverHit
Indicates that a creative work has achieved significant popularity or success across multiple distinct audience segments, genres, or markets beyond its original target.
-
B.
featuresCrossoverWith
chosen
Indicates that one entity includes or participates in a crossover event or collaboration with another entity.
-
C.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
D.
crossesOverWith
Indicates that one entity intersects or overlaps with another, typically by passing across or through its path, boundary, or extent.
-
E.
crossingStyle
Indicates the manner or method by which one entity crosses or traverses another (such as a boundary, path, or medium).
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 8:31 a.m.