Triple
T33062848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House Reef at Panagsama |
E846017
|
entity |
| Predicate | typicalEntry |
—
|
GENERATED |
| Object | shore entry |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 1, 2026, 1:25 a.m.