Triple
T27603624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnham-on-Crouch RNLI lifeboat station |
E700118
|
entity |
| Predicate | hasVolunteerCrew |
P49934
|
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: [Burnham-on-Crouch RNLI lifeboat station, hasVolunteerCrew, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolunteerCrew Context triple: [Burnham-on-Crouch RNLI lifeboat station, hasVolunteerCrew, true]
-
A.
hasVolunteerPersonnelFrom
Indicates that an entity receives or utilizes volunteer personnel supplied by another entity or source.
-
B.
hasVolunteerRescueSquad
chosen
Indicates that an entity is served or supported by a volunteer-based rescue or emergency response squad.
-
C.
hasExtendedCrew
Indicates that an entity is associated with an additional or supplementary group of crew members beyond its primary crew.
-
D.
intendedCrew
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
-
E.
hasCrewCapacity
Indicates that an entity is capable of accommodating a specified number of crew members.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 2:09 p.m.