Triple
T15384710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banshee Boardwalk |
E367887
|
entity |
| Predicate | hasLakituRecovery |
P118560
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Banshee Boardwalk, hasLakituRecovery, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLakituRecovery Context triple: [Banshee Boardwalk, hasLakituRecovery, yes]
-
A.
hasRestoration
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
B.
recoveryCapability
Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
-
C.
hasRestorationActivities
Indicates that an entity carries out, is involved in, or is associated with actions aimed at restoring or rehabilitating another entity or resource.
-
D.
isRecoveringFrom
Indicates that one entity is in the process of regaining health, function, or normal condition following an illness, injury, or adverse event associated with another entity.
-
E.
capsuleRecovery
Indicates the action or process of retrieving a capsule after its use, mission, or deployment.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7397188190bde42b897ab4b5b4 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.