Triple
T796377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nēnē |
E17031
|
entity |
| Predicate | recoveryMethod |
P19129
|
FINISHED |
| Object | captive breeding |
—
|
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: captive breeding | Statement: [nēnē, recoveryMethod, captive breeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoveryMethod Context triple: [nēnē, recoveryMethod, captive breeding]
-
A.
boosterRecoveryMethod
Indicates the method or process used to recover a rocket booster after its mission.
-
B.
recoveredFrom
Indicates that an entity has returned to a normal or improved state after previously experiencing or being affected by another specified condition, event, or problem.
-
C.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
-
D.
restoredBy
Indicates that an entity has been returned to a previous or improved state through the actions or intervention of another entity.
-
E.
restored
Indicates that an entity has returned another entity to a previous or improved state, condition, or position after damage, loss, or alteration.
- 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_69a49378b9c48190adbf5f62e5b7aca1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a7b172e88190a26d31c9075b81fb |
completed | March 1, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69a4a5122a008190b0c621b7bc588d41 |
completed | March 1, 2026, 8:44 p.m. |
| PDg | Predicate description generation | batch_69a4a5bed20c81909ecc28bf42594e72 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:38 p.m.