Triple
T3363404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coral Sea Marine Park |
E70776
|
entity |
| Predicate | reproclaimed |
P47582
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Coral Sea Marine Park, reproclaimed, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reproclaimed Context triple: [Coral Sea Marine Park, reproclaimed, 2013]
-
A.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
B.
recommissioned
Indicates that something previously deactivated, retired, or out of service has been restored and formally returned to active use or operation.
-
C.
recreated
Indicates that an entity has been created again or restored, typically after being removed, destroyed, or significantly altered.
-
D.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
E.
reincorporated
Indicates that an entity has been formed again or brought back into existence as a corporation after having previously ceased or changed its corporate status.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb26a5a508190948932769de0dbb3 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada698eeb48190a1f5762fdd3b7b63 |
completed | March 8, 2026, 4:40 p.m. |
Created at: March 8, 2026, 3:13 p.m.