Triple
T17670367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helike |
E440503
|
entity |
| Predicate | remainsReportedVisibleFor |
P16211
|
FINISHED |
| Object | centuries after submergence |
—
|
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: centuries after submergence | Statement: [Helike, remainsReportedVisibleFor, centuries after submergence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remainsReportedVisibleFor Context triple: [Helike, remainsReportedVisibleFor, centuries after submergence]
-
A.
visibleRemains
Indicates that some physical remnants of an entity or event can still be seen or visually detected.
-
B.
gainedVisibilityIn
Indicates that an entity became more publicly known, noticeable, or prominent within a particular context, medium, or audience.
-
C.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
D.
visibilityDuration
chosen
Indicates the length of time for which something remains visible or observable.
-
E.
visibleAfter
Indicates that one entity becomes perceptible or can be seen only after another specified event, time, or condition has occurred.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f67f6188190a978c7c9f462064d |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:59 a.m.