Triple
T33062848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Reef at Panagsama |
E846017
|
entity |
| Predicate | typicalEntry |
P44366
|
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: [House Reef at Panagsama, typicalEntry, shore entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEntry Context triple: [House Reef at Panagsama, typicalEntry, shore entry]
-
A.
typicalEntryType
chosen
Indicates the usual or standard category or kind of entry associated with something.
-
B.
typicalEntryList
Indicates a relationship where an entity is associated with a standard or representative list of entries that are commonly or normally linked to it.
-
C.
typicalEntryPost
Indicates that an entity is the usual or standard post or position at which another entity typically enters or begins an activity or process.
-
D.
typicalEntryFile
Indicates that a given file is the standard or primary entry point typically used to start or access something (such as a program, project, or package).
-
E.
typicalItem
Indicates that an item is a representative or characteristic example of a broader category, class, or set.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:25 a.m.