Triple
T33951136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairbourne Beach |
E870441
|
entity |
| Predicate | hasActivityZone |
P165361
|
FINISHED |
| Object | dog-friendly sections |
—
|
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: dog-friendly sections | Statement: [Fairbourne Beach, hasActivityZone, dog-friendly sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivityZone Context triple: [Fairbourne Beach, hasActivityZone, dog-friendly sections]
-
A.
hasActivityRegion
Indicates the geographic or spatial region within which an activity occurs or is applicable.
-
B.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
C.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
D.
has activity
Indicates that one entity performs, exhibits, or is engaged in a particular action, behavior, or process associated with another entity.
-
E.
activityZone
chosen
Indicates that something is located within, associated with, or designated as a specific area where a particular activity or set of activities takes place.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:49 a.m.