Triple
T6221565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra Nova |
E139125
|
entity |
| Predicate | hasEnhancedRecoveryMethods |
P19129
|
FINISHED |
| Object | water injection |
—
|
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: water injection | Statement: [Terra Nova, hasEnhancedRecoveryMethods, water injection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnhancedRecoveryMethods Context triple: [Terra Nova, hasEnhancedRecoveryMethods, water injection]
-
A.
recoveryMethod
chosen
Indicates the method or process by which something is restored, retrieved, or brought back to a previous or functional state.
-
B.
supportsSignInMethod
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
-
C.
recoveryCapability
Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
-
D.
confirmationMethod
Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
-
E.
boosterRecoveryMethod
Indicates the method or process used to recover a rocket booster after its mission.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062bddb688190add53172a7445d01 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.