Triple
T4384455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearling, Testimony of an Island Economy |
E99206
|
entity |
| Predicate | bufferZoneType |
P36294
|
FINISHED |
| Object | urban and marine buffer zones |
—
|
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: urban and marine buffer zones | Statement: [Pearling, Testimony of an Island Economy, bufferZoneType, urban and marine buffer zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bufferZoneType Context triple: [Pearling, Testimony of an Island Economy, bufferZoneType, urban and marine buffer zones]
-
A.
bufferZone
Indicates the existence of an area or region that serves as a protective or separating space between two or more entities or activities.
-
B.
ticketingZoneType
Indicates the type or category of ticketing zone that applies within a given area or context.
-
C.
zoneType
chosen
Indicates the classification or category of a zone that specifies its type or functional designation.
-
D.
blockSize
Indicates the size or capacity of a discrete block unit within a larger structure or system.
-
E.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35263970c8190904ee20d81715833 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:19 p.m.