Triple
T36796580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snap Ads |
E909199
|
entity |
| Predicate | appearsBetween |
P197433
|
FINISHED |
| Object | user-generated content |
—
|
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: user-generated content | Statement: [Snap Ads, appearsBetween, user-generated content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsBetween Context triple: [Snap Ads, appearsBetween, user-generated content]
-
A.
currentBetween
Indicates that the current value of a quantity lies within a specified range between two boundary values.
-
B.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
C.
takesPlaceBetween
Indicates that an event or interaction occurs within the temporal or spatial interval defined by two reference points.
-
D.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
E.
appearsBefore
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
| PDg | Predicate description generation | batch_69fe9137730c81909d1d57c30566c89a |
completed | May 9, 2026, 1:43 a.m. |
Created at: May 3, 2026, 4:12 p.m.