Triple
T24145634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raploch |
E598374
|
entity |
| Predicate | hasRegenerationStatus |
P155007
|
FINISHED |
| Object | regeneration area |
—
|
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: regeneration area | Statement: [Raploch, hasRegenerationStatus, regeneration area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegenerationStatus Context triple: [Raploch, hasRegenerationStatus, regeneration area]
-
A.
hasRegenerationType
Indicates the specific kind or method of regeneration associated with an entity.
-
B.
hasRegenerationCycleWith
Indicates that two entities are linked by a recurring regeneration or renewal process that they undergo together or in relation to each other.
-
C.
hasMultipleRegenerations
Indicates that an entity has undergone more than one process of regeneration or renewal.
-
D.
regeneratedWhen
Indicates that an entity is brought back, restored, or recreated at a specific time or under specific conditions.
-
E.
canRegenerate
Indicates that an entity has the ability to regrow or restore lost or damaged parts of itself.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00a37b881909e31f85a667e6d83 |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:29 p.m.