Triple
T12705677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eel Garden (dive site) |
E303577
|
entity |
| Predicate | hasEntryPoint |
P6140
|
FINISHED |
| Object | shore entry |
—
|
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: shore entry | Statement: [Eel Garden (dive site), hasEntryPoint, shore entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEntryPoint Context triple: [Eel Garden (dive site), hasEntryPoint, shore entry]
-
A.
hasEntryOn
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
B.
entryPointFor
Indicates that one entity serves as the access or starting location through which another entity is entered, initiated, or reached.
-
C.
hasEntrance
chosen
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
D.
hasEntryRequirement
Indicates that one entity specifies conditions or qualifications that must be met before another entity is allowed access, participation, or admission.
-
E.
hasMainSeriesEntry
Indicates that an entity is a primary or canonical installment within a larger series or sequence of related works.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961f1adec8190a53c80e9556b3fe0 |
completed | April 10, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.