Triple
T25977989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petroica traversi |
E645991
|
entity |
| Predicate | recoveryProgramStart |
P53924
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Petroica traversi, recoveryProgramStart, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoveryProgramStart Context triple: [Petroica traversi, recoveryProgramStart, 1970s]
-
A.
recoverySystem
Indicates a system or mechanism responsible for restoring a previous state, function, or data after a failure, loss, or disruption.
-
B.
recovery
chosen
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
C.
reconstructionProgram
Indicates a program or initiative designed to rebuild, restore, or structurally improve something that has been damaged, degraded, or is otherwise in need of renewal.
-
D.
launchAndRecovery
Indicates a relationship where one entity is responsible for both deploying (launching) another entity into operation and subsequently retrieving (recovering) it afterward.
-
E.
recoveryDate
Indicates the date on which a recovery process or restoration of a prior state is completed or officially recorded.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6050aa9948190a439fb09ff4e0ed1 |
completed | May 2, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:52 a.m.