Triple
T33462819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesus Green |
E856966
|
entity |
| Predicate | hasSwimmingPoolType |
P167899
|
FINISHED |
| Object | lido |
—
|
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: lido | Statement: [Jesus Green, hasSwimmingPoolType, lido]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSwimmingPoolType Context triple: [Jesus Green, hasSwimmingPoolType, lido]
-
A.
hasSwimmingPool
Indicates that the subject possesses or includes a swimming pool as one of its features.
-
B.
hasSwimmingAreaType
chosen
Indicates that an entity’s swimming area is classified as a specific type or category (e.g., indoor pool, open water, designated beach zone).
-
C.
mainSwimmingPoolLength
Indicates the length measurement of the primary swimming pool associated with an entity.
-
D.
homePool
Indicates that an entity is associated with or belongs to a primary or default pool, typically used as its main or originating pool.
-
E.
hasAquaticCentre
Indicates that one entity possesses, contains, or is associated with an aquatic centre facility.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4d5269081909a5c6ba07ad90283 |
completed | May 3, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.