Triple
T3363405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coral Sea Marine Park |
E70776
|
entity |
| Predicate | managementPlanCommenced |
P35708
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Coral Sea Marine Park, managementPlanCommenced, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managementPlanCommenced Context triple: [Coral Sea Marine Park, managementPlanCommenced, 2018]
-
A.
hasManagementPlan
Indicates that an entity is associated with a defined management plan specifying how it should be overseen, maintained, or administered.
-
B.
planningStarted
chosen
Indicates that the process of planning for a particular task, project, or event has been initiated.
-
C.
managedIn
Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
-
D.
managedAct
Indicates that one entity oversaw, directed, or was responsible for carrying out a particular action or activity.
-
E.
managedUntil
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
- 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_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. |
Created at: March 8, 2026, 3:13 p.m.