Triple
T31577987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Register of Marine Species |
E805747
|
entity |
| Predicate | isContinuously |
P178834
|
FINISHED |
| Object | updated |
—
|
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: updated | Statement: [World Register of Marine Species, isContinuously, updated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isContinuously Context triple: [World Register of Marine Species, isContinuously, updated]
-
A.
isContinuous
Indicates that a function, process, or relationship changes smoothly without abrupt jumps or breaks over its domain.
-
B.
canBeContinuous
Indicates that something has the potential to occur, exist, or be maintained without interruption over a continuous range or period.
-
C.
continuesFor
Indicates that an event, state, or process persists or remains in effect for a specified duration or period.
-
D.
hasContinuo
Indicates that a musical work, section, or passage includes a basso continuo part or accompaniment.
-
E.
hasRepresentationContinuity
Indicates that one entity maintains a consistent or continuous representational relationship with another across time, context, or state changes.
- F. None of above. chosen
Provenance (4 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 30, 2026, 10:22 p.m.