Triple
T38235000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deal Beach |
E1013595
|
entity |
| Predicate | isLessPopularWith |
P26006
|
FINISHED |
| Object | day-trippers from outside the area |
—
|
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: day-trippers from outside the area | Statement: [Deal Beach, isLessPopularWith, day-trippers from outside the area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLessPopularWith Context triple: [Deal Beach, isLessPopularWith, day-trippers from outside the area]
-
A.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
B.
isLessPreferredBy
chosen
Indicates that one option, item, or entity is chosen or favored less than another by a particular agent or group.
-
C.
isLesserKnown
Indicates that one entity is less widely recognized, famous, or familiar than another comparable entity.
-
D.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
E.
isLessCommonThan
Indicates that one item occurs, appears, or is observed less frequently than another item.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.